I am using firebase crash reporting API in my Android app.
Crash reporting is working fine and showing the error on crash reporting dashboard.
But I am not able to upload mapping.txt file on the firebase.
I got mapping file from below location.
\app\build\outputs\mapping\release\mapping.txt
The firebase dashboard image is below
I contact firebase support team and they give me some suggestions as bellow.
Please retry using an incognito window, or do the following when uploading proguard mapping file:
– log out of your dashboard
– clear your browser cache
– disable all plugins/extensions/addons
– restart the browser
– log in again
If you are still having issues:
– try to connect using other browser or network
– open your JavaScript console and see if there are errors
– send us your browser/os version
– send a screenshot of errors in JavaScript console if possible
I solved my issue when I try to upload a file from another browser.
Hope this will help anyone who is facing the same problem like me.
Related
I'm trying to upload an apk for distribution on firebase but I get this error instead:
"There's been an error processing your distribution. Ensure you're uploading a valid IPA or APK and try again. Additional information about this error: Invalid APK file."
I'm indeed trying to upload an apk (which by the way, works fine on device). I thought the issue could be related to the android keystore, but that seems okay too. Can't find much more info on this online. Any suggestions?
There could be various reasons for this type of issue and you can try the below methods to solve the problem.
Try to upload apk via a google chrome OR any other browser. Reason for saying this is sometime problem is your session invalid. Using any different browser such as firefox,IE etc. would create new session and allow to upload apk.
Sometimes it happens due to low internet speed speed but it's rare.
It could be happened with the application icon. You must need to be set in the AndroidManifest.xml file
You can contact to firebase support team if above doesn't work. Link
Suddenly from 3 days, I am not able to use Google Internal App sharing. Loading App sharing page fails with error "unexpected error". Is there anyone else who faced this issue? and have some workaround?
Note:
I am aware that I should raise this issue in Google support, but they are taking too much time to respond. Meanwhile, I am just searching for workarounds or possible reasons for it.
I have tried all possible solutions which are already there on the Web, like incognito mode, clearing cache, etc.
In my network those who already have play store accounts are also getting the same issue.
The API gateway still seems to work. I was able to upload a test apk/aab via fastlane.
It's an easy setup. Then use the upload_to_play_store_internal_app_sharing command to upload the apk/aab
I have developed and put an android application in Google Play store.
Someone inform me that the app is crashing while doing something in application.
As a application developer,
How to find the problem and fix it in android?
Is there any tool or framework to debug the crashed app in android?
There are many sdks out there which can be incorporated in your app.
You can use
1. crashlytics
2. localytics
3. crittercism
Its always a best practice to include some analytics tools in your android application to know where users are spending a lot of their time. I personally like flurry Analytics.
Since you have already uploaded the apk you should check it out in the google play developer console. Even google will provide the crash data, and it is the only resource you have.
As far as fixing the application goes you can do it only by uploading a new apk and asking the users to update the app.
ACRA is a right choice for you to analyze the crash report. Please refer the following link to implement in your project.
https://github.com/ACRA/acra
And also, You can find the crash report in your developer console if the the user has sent the crash report while force closing of the application.
Please ensure that you have not enabled the proguard. if you have enabled proguard, try decode the lines using the following link
http://developer.android.com/tools/help/proguard.html#decoding
My application is going to be published in the market. I want to know if is there any standard lib or procedure we can follow for collecting logs of published apps.It should not only collect the crash logs but also have to log apps critical events and send to a predefined backend server. And my source code is obsucated using proguard.
Please suggest an efficient way if anyone has done it.
If you're after free and open source check out the following lib: ACRA.
What is ACRA?
ACRA is a library enabling Android Application to automatically post their crash reports to a GoogleDoc form(now deprecated, but they instead use Acralyzer, which is much better). It is targetted to android applications developers to help them get data from their applications when they crash or behave erroneously.
Here you can find their GitHub page which lists all the features of ACRA if you want to decide if this is for you.
I want to know if is there any standard lib or procedure we can follow for collecting
logs of published apps.It should not only collect the crash logs but also have to log apps
critical events and send to a predefined backend server.
There is an open Source Library called Apache log4j. So by using this Api you can store the all kind of Log into a Text or .Xml file and will be stored in your given path.
You can find the document Log4j
You can download jar from Here
And if you released your application then you can get the Crash log on Google Play Developer Console.
Or else you can use Android Crash report using ACRA to get the Crash log in terms of Excel
Hope this will help you.
You can use Hockey App for retrieving crash reports from users. You can use this link also
I'm using a new version of the Facebook SDK, in my android app, where the Util.java class is deprecated and hence I can't find the ENABLE_LOG variable at all (which all the current solutions online ask us to find and change). Instead I had to enable log in the facebook manifest using . And even then there was no log error. This error (misconfiguration) occurs even though I've used the keyhash generated by the .keystore file which I used to sign my app before release.
The issue got resolved only when I deleted the Facebook app from my phone, which is ridiculous. Does anyone know the actual solution to this problem?