I'm running a build from the Android Things Console built with several custom apks
One of the apps is failing with "{AppName}" has stopped. Open app again" The cause appears isolated to only one Configuration.
I'm trying to get to root cause, normally I would run "adb logcat" to view full details with android. Is adb logcat support with Android Things build? Is a mechanism such as logcat available in Android Things when built with a build from the Android Things Console? If not, is there an alternative?
ADB is available on development images of Android Things, not on production builds. You can change which one in the console. You can also add crash reporting tools like Crashlytics which will provide crash reports for you.
Related
It's a weird situation. I have a react native app that has a test and production environment. On the production side, my app is correctly integrated with crashlytics. But when I try to integrate on test apk, I see only "App detected and we're waiting for a crash!"
SS
Test and prod use the same application, the only difference is google-service.json files. I've not found anything. Please help.
Some notes:
I've tried on emulator and physical devices.
When I try to see dashboard for prod build, I can see correctly.
I don't think that it is related by package versions(Because it works on prod). So I didn't put those.
I 've seen " Crashlytics automatic data collection DISABLED by API" with adb logcat -s FirebaseCrashlytics command
When running the app, if you see the "App detected and we're waiting for a crash!" message, that means that the SDK was able to connect with the back end. But something could be preventing the SDK from sending crashes.
The first thing to do would be checking if the mapping file contains the parameter firebase_crashlytics_collection_enabled and if it is set to false. Check this document.
If so, you can override this parameter opting in with the code:
Firebase.crashlytics.setCrashlyticsCollectionEnabled(true)
So I just spend the whole night messing up and reinstalling android studio and vscode and flutter cause I was trying to build an apk for my app that's ready enough to pass out to some friends for testing. when my phone is connected to my computer I can debug my app no problem so I thought no big deal lets push out an apk and show off my work. What a nightmare this has been and still is.
I followed this step by step guide to building an android app... https://docs.flutter.dev/deployment/android
So once I finally got all the mystery errors out enough for it to build an apk I copied the file over to my phone and installed it. Well soon as it installed and still on the pop up I see 2 buttons, Close and Open, only open is greyed out. I cant open my app up.
I tried changing the targetSdkVersion down to my phones android version.I tried building out every possible version and appbundle and apk for all the processors and I just cant seem to get a variant to open. I have the key.properties file all linked up, I used the keytool like in the guide.
Has anyone else build out flutter app but cant open it? I'm stumped... The first few attempts I was getting extra popups for googles play protect so I went and turned off that feature. Ive had my phone in developer mode for years now so I know unknown sources are allowed.
It installs fine, but doesnt create an icon anywhere to be used. Once i exit out of the original install popup the only way Id know it was on my device is to go into settings/apps and find it there, and in there the only options are uninstall and force stop which is also greyed out. So the app is unuseable
I am new to running instant app. I have created a new "Hello World" project with instant app support, according to android developer documents.
But, when running "instantapp", the following error occurs:
I would appreciate it if anyone could help.
Note: There is a known issue running Instant Apps on the emulator image that includes the Google Play Store which will give this same error. For now, please use the emulator without Play Store.
Google Play Services giving statusCode=API_UNAVAILABLE means your device is not able to run Instant Apps for one reason or another. For example, you are not using a supported device or you are not in a launched country. Please see here for a list of supported development devices and here for a list of countries Instant Apps are available in.
The emulator should still work for development and will run outside of any restrictions. For instructions on setting up an emulator for Instant App development see here:
https://developer.android.com/topic/instant-apps/getting-started/setup.html#setup-emulator
I built an android application and signed the apk following all the steps on this tutorial. Even though the APK builds successfully after installing it on a mobile device it fails to load. I only get a white blank screen. I've searched for solutions and tried most of the suggestions but with no luck.
I then decided to start the project from scratch and guess what? the problem still persists. What could I have possible done wrong? I don't really know where to look because I don't even get an error message.
Please help???
I would try debugging that with a tool like GapDebug (https://www.genuitec.com/products/gapdebug/). I would:
Download and install GapDebug.
Attach your device to your PC/Mac via a USB cable.
Deploy your APK to the device and run it.
In GapDebug, choose your app as the app you want to debug.
At this point you may already see one or more errors showing up in the GapDebug console. If not,
On the device, restart the app.
Check the GapDebug console for errors.
We have an app on google play, and we are about to publish update, but testing update on JB device resulted in UnsatisfiedLinkError when calling System.loadLibrary("ourlib") in our code. ourlib is library compiled by us using NDK. This error shows only on 4.1 devices.
I suspect that it has something to do with new security on JB, app was first installed with Google Play with lets say version 1, and then reinstalled with version 2 using adb or from device using apk.
I could not find anything related to that on google, what could be the problem?
this problem
http://code.google.com/p/android/issues/detail?id=35962
looks similar but it appears that it was an error in google play actually.
Does that mean that you are trying to use standard/system library? Maybe the version of the library that you are trying to load does NOT contain particular functionality that you intend to use. Check android docs when the functionality became or stopped being available.
The solution is to use:
$ adb install -r -l my.apk
this makes apk to be reinstalled with use of forward-lock (aka. copy protection), I supose that because apk was upladed to google play with copy protection enabled then also forward-lock option in adb had to be added. I know JB introduced some changes with forward lock so this might be the case. I dont know internals of what really caused this problem, but above seems to work.