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
On low memory devices (my Sony Neo and a friend's Sony Arc S), there's a frequent crash that seems to come from low memory (happens on no other devices): java.lang.RuntimeException: Unable to create application com.brainydroid.daydreaming.ui.App: com.google.inject.CreationException: Guice creation errors: : at com.brainydroid.daydreaming.ui.App.onCreate(App.java:47)
If I remember well this appeared when we started loading the questionnaires from DB when opening the Dashboard (for questionnaire button status). If we find a way to alleviate app launch, like caching the status of questionnaires, or using providers to avoid Guice injecting absolutely everything on app creation (because our Dashboard depends on absolutely everything), it should solve the problem. This is also applicable generally for the whole app.
The text was updated successfully, but these errors were encountered:
On low memory devices (my Sony Neo and a friend's Sony Arc S), there's a frequent crash that seems to come from low memory (happens on no other devices):
java.lang.RuntimeException: Unable to create application com.brainydroid.daydreaming.ui.App: com.google.inject.CreationException: Guice creation errors: : at com.brainydroid.daydreaming.ui.App.onCreate(App.java:47)
See the ACRA report: http://crash-reports.daydreaming-the-app.net/acralyzer/_design/acralyzer/index.html#/reports-browser/daydreaming/bug/44071a0bba8a8e89b1c7a0821553e9d1
If I remember well this appeared when we started loading the questionnaires from DB when opening the Dashboard (for questionnaire button status). If we find a way to alleviate app launch, like caching the status of questionnaires, or using providers to avoid Guice injecting absolutely everything on app creation (because our Dashboard depends on absolutely everything), it should solve the problem. This is also applicable generally for the whole app.
The text was updated successfully, but these errors were encountered: