-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crashes on startup in apk but is working on emulator #33
Comments
Hi, Once shouldn't need any proguard configuration, as it doesn't use reflexion or similar things. Do you have the stacktrace for the crash and I can look into this? Are you sure you've called initialise before this code is executed? |
I called Once before the code is executed:
And here is my Once code below:
How do I get a stacktrace for something that only crashes on apk? |
You should be able to set debuggable to true in your release build in your build.gradle file:
Then inside Android Studio if you have the device your running it on connected then you should be able to see the crash in the logcat window. Unfortunately without a stacktrace there's not much I can do. |
Also you should probably initialise the library inside your application class, rather then every time the activity is created. |
Ok I put in debuggable true and got this stacktrace:
|
As far as I can see that doesn't look to be related to Once. Can you isolate the crash to a particular change? i.e. does removing a line of code that calls once fix this crash? |
Thanks! Turns out it was gradle not packing the apk right. I unistalled and repacked and it seems to be working now. |
@yofu1234 could you talk more about the solution ? |
did you find any solution? |
I used
if (!Once.beenDone(Once.THIS_APP_INSTALL, showAppTour)) { ... Once.markDone(showAppTour); }
and it works fine in release build on the emulator but when I compile it into an apk, it crashes on startup.
Is their a proguard line of code that Once needs?
The text was updated successfully, but these errors were encountered: