-
Notifications
You must be signed in to change notification settings - Fork 161
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
Can't create APK #99
Comments
With those changes it compiles and does not crash for me: #100 |
Hi, did you get it working? I'm using studio3 branch but APK is crashing every time at the beginning. I can compile it succesfully. Same result in emulator and in Hardware. Just wondering if there is something wrong in my android studio& setup in general. |
Kind of. After AdrianLxM made the changes I'm able to make a signed APK and install it separate from Android Studio, (via email it to myself and open) and it will run on my phone. But if I try and use USB to put it on phone to use debugging or what not, it crashes every time either in the emulator or by phone. I was able to enter the debugger on my watch by enabling debugging by wifi though. Just can't get into the debugger for the code that is run on the phone. |
I was able to get my own APK working after disabling "Instant run". If instant run was enabled, I got following error: |
When I try and compile the code and build an APK using Android Studio 3.0.1, I get a error message:
Error:Unsupported method: BaseConfig.getApplicationIdSuffix().
The version of Gradle you connect to does not support that method.
To resolve the problem you can change/upgrade the target version of Gradle you connect to.
Alternatively, you can ignore this exception and read other information from the model.
If I increase the gradle version to 2.3.2 as seen on this website:
https://stackoverflow.com/questions/44546849/unsupported-method-baseconfig-getapplicationidsuffix
I can get it to compile, but the app crashes immediately when I try and run the build on my phone. Any suggestions?
The text was updated successfully, but these errors were encountered: