Some context:
I have an android application in production and in the past weeks i'm seeing an increase of reports in firebase crashlytics from android emulators calling activities outside normal flows ( for example in a chat application, starting the profile of a contact without going first to the contact chat. )
The app crashes because is expecting some data that is not currently available, but my question is:
Can google play scanner to check for virus in apks be the reason behind this runs in emulators ? Is someone having this kind of crashes too? Or i have one user testing my apk with an emulator ?
Thanks in advance.
Related
For testing, a project was created in Firebase and two applications (for iOS and Android) were published. Testers have also been added, who have successfully received invitations to participate in testing by email.
When clicking on the link in the invitation, a window opens (first screenshot), which successfully displays some information about the application under test. Immediately, the user is offered to download the App Tester application or download the application being tested directly. When you click on both buttons, the same error appears (second screenshots).
ps What can it be connected with? I am currently in Russia, but I tried downloading using a VPN - the same result.
pss the application is written in Flutter, it was also initialized as a Flutter application in Firebase
Yes, the download does not start due to the fact that I am geographically located in Russia, which is sad. The download has started from the VPN of another country.
ps Apparently the VPN, under which the application did not load, also sent requests through Russia
This is not a duplicate of the question: Unfortunately MyApp has stopped. How can I solve this?
The problem is when running an app on independent device, not connected to the computer.
Basically, I have a Flutter app that works fine in Run mode and Hot Reload of Android Studio and on the connected device.
However, when I created .apk file, placed this file to the Google Play Market and downloaded the app into the smartphone, the app does not work.
It looks like this: I press "Open" on the icon of the mobile app, I see a message "App has stopped" with available options "Open app again" and "Send feedback".
My questions are:
(1) How is it possible to check what exact failure the app has?
(2) Is it possible to use Fabric for Flutter apps? If yes - does this require the same actions as for an Android mobile app?
Thank you in advance for your support.
Sincerely,
Mary
Try this:
https://pub.dev/packages/firebase_crashlytics
Firebase crashlytics:
Whenever your app crashes or throws an error, the firebase crashlytics library will capture it and sends the details to firebase.
Make an account on firebase, and create an app. Click on Crashlytics on the side menu and complete the setup. It should start logging crashes to your firebase account.
Background:
I am getting the same issue. It works on many phones. But some of my users keep getting the error "Unfortunately myApp has stopped working". I just connected it to firebase_crashlytics. This works very well in Native Android apps. I am trying for the first time in Flutter.
The developer console for android has functionality for reporting runtime crashes if users decide to report a crash. Other frameworks has similar features that sends crash-reports without involving the user.
Does anyone know of a way to report installations or upgrades that has failed? With android 5.0 I am getting more and more user-reports of failed installs, but it is hard to obtain logs from non-technical users of my app.
You cannot detect whether or not an installation has failed yourself, because there is no way to execute code before your app is actually installed. So the logical app to do such a thing would be the market app triggering the install (i.e. Google Play). This not only knows when each installation starts, but also knows all details about the apk to report to the right developer.
Unfortunately however, Google play does not support this currently (as far as I know) and hence you cannot detect failed installs.
On older Android phones you could ask users is to install a "logcat app" and email the logs to you for analysis, but this will only work for devices older than Jelly bean. (Read this Link)
The best solution I can come up with (Mac only) is to ask users to install AndroidTool, press one button to generate a bugreport and email that to you. Not great, but for now the best you can do.
You can build an api that reports successful installation. Just call the api in onCreate of first activity. I don't think there is need to collect log on why the installation failed, is it needed ? You can do the same for upgrade, call an api one time from upgraded code.
I have created a test build of a GDK Glass app that I want to deliver to a few test users. However the app disappears after a reboot. Logcat shows this:
08-19 18:18:18.256: I/GlasswareSyncAdapter(978): Uninstalling Glassware ID #6DBADA7634397F00 (com.example.demo).
A look at the issue tracker explains that this is caused due to the fact that the MyGlass app didn't install this app and that the app thus isn't linked to the user's account.
Are there any workarounds? With a submission process of over a month how can we get our app tested properly?
The submission process should be less than a month at this point. I suggest that once you think you have things working, you submit the app.
Once submitted, you'll be working with the Review Process Team. They are able to create a whitelist (certainly of accounts, and possibly based on a list you can control through a Google Group) of who will be able to see the app on their MyGlass page. This will also allow you to test the app, including the auth flow, using the actual installation process.
It seems like this issue only occurs when the application you are side loading has been submitted to Google for approval. Just change change the package name of the APK you want to sideload and your problem should be solved.
I have an android app uploaded in google marketplace.
I have been reported an error from a user, which happens only in a specific device.
It is not a crash, the application just doesn't work exactly as expected. I have tried to reproduce the error using the emulator with the exact android version he's using and it works fine.
I am sure I could determine the problem If I'd have access to the Logcat entries.
I suppose the answer is negative, but it is any way the user can get these entries and send them to me? ( of course I cannot tell him to install eclipse or adb to gather the log entries ).
What is the best practice to be able to get error information from your app, once it is uploaded to the market? ( I don't mean crashes where an error report can be sent by android, just something that it is not working as expected ).
The application aLogcat can do the trick.
https://play.google.com/store/apps/details?id=org.jtb.alogcat&feature=nav_result#?t=W251bGwsMSwxLDMsIm9yZy5qdGIuYWxvZ2NhdCJd
And I tested it on my 4.1.1 device.
(I don't know how to post this as a comment instead of answer)
there are several apps on android market that allows to get logs and send them by email or upload them to dropbox... I used this one: https://play.google.com/store/apps/details?id=com.xtralogic.android.logcollector