You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 7, 2023. It is now read-only.
There should be an option through cli to delete ~/.turtle/workingDir or clear workingDir/{platform}/sdk#/packages and/or node_modules
Motivation Behind Feature - Feature Description
Having installed a plugin previously (with expo install) it didn't work for me in the end, so I removed it. However when testing something else the previously removed plugin was crashing my app unexpectedly as I found out from adb log while the app was running (lateinit property {pluginname} has not been initialized). This behaviour happened after a GoogleSignin native activity popped up and upon dismissing it, my app's activity tried to come to foreground and then it crashed. So after hours of searching for the cause I found that if I remove ~/.turtle/workingDir and re-run turtle build:android there would be no crashes when reproducing a specific app flow.
Alternatives or Workarounds
Manually deleting node_modules from the project directory and also the workingDir in ~/.turtle/workingDir and re-installing and re-building.
The text was updated successfully, but these errors were encountered:
Feature Request
There should be an option through cli to delete
~/.turtle/workingDir
or clearworkingDir/{platform}/sdk#/packages and/or node_modules
Motivation Behind Feature - Feature Description
Having installed a plugin previously (with
expo install
) it didn't work for me in the end, so I removed it. However when testing something else the previously removed plugin was crashing my app unexpectedly as I found out from adb log while the app was running (lateinit property {pluginname} has not been initialized
). This behaviour happened after a GoogleSignin native activity popped up and upon dismissing it, my app's activity tried to come to foreground and then it crashed. So after hours of searching for the cause I found that if I remove~/.turtle/workingDir
and re-runturtle build:android
there would be no crashes when reproducing a specific app flow.Alternatives or Workarounds
Manually deleting node_modules from the project directory and also the workingDir in ~/.turtle/workingDir and re-installing and re-building.
The text was updated successfully, but these errors were encountered: