Firebase has very annoying interface to work with issues. There is no option to move to specific issue in cluster etc.
Is there any way to export crash reports from Firebase Crash Reporting section? Or may be you can give me a hint how to move to specific issue in cluster instead of clicking all issues one by one :).
Related
I am using Firebase Crashlytics in my Android app. At this point, my app is exclusively available as an internal test version which is only visible to 3 known testers (set up within Google Play console). Everything works well and I see my crashs in the console.
However, I keep getting crash resports of totally unknown users who are not registered as testers. I can see these users in the Authentication tab in the Firebase console. Here is a snippet:
I see crash reports of totally unknown devices which definitely do not belong to any of my registered testers. They are definitely not coming from an emulator.
QUESTION: Does anyone have an idea where these users come from and how they can access an app in the internal test track?
OK, if anyone has the same question: I got this answer here:
Google/Android runs some automated bot tests on your app.
Would be great if that were documented somewhere...
I am a beginner in android and was working on a small project where multiple user sign up and perform different action like posting, liking, commenting. All data being stored on fire-base database and storage. I want to build an 'Events module' in the app, that helps each user set their own event, descriptions, time and days to give them reminders. I am unable to work as I don't know where to start. What should I use. I tried searching alarm manager but I really am not getting it so much. Many people have worked using SQLlite and alarm manager but I don't want to use sqlLite. Help me what should I start.
I found the answer to this a day after. The reason why we need to choose sqlite and not firebase is because alarms are locally stored on our mobile devices. Sqlite helps in such process whereas firebase works as cloud which is usually not recommended and used for alarms or calendars!!! Cheers
The browser console runs very slowly for me.
I usually have a page open on a project's database page and another one on its functions log.
I was wondering if there are any (safe) alternatives to the online console?
If you use VSCode, the Firebase Explorer extension usually loads faster and avoids some context switching.
Have found this twice from google so thought I would update with this tool
https://firefoo.app/
14 day free trial but so far it's worth the small monthly fee
Help!
I’ve been trying to transfer an app for a month now to a client and he’s getting angry! The last box in App Store connect about the TestFlight builds won’t grt ticket, and I don’t know what to do. I’ve tried everything. All builds are gone, all info from localizations, I’ve made countless updates, everything. I contacted Apple support but they’ve just kept passing me to different levels of support so far. I don’t know what do to. Is there a way to manually transfer it? Like if I removed mine from sale, and uploaded it on the clients side? And help is appreciated, thanks!
for transferring your app to the diff account.
All the test flight build has to be deleted manually.
All the test details has to be wiped off.
All the App information has to be cleaned in the app information section.
But i could see that you didn’t deleted the test flight build properly. thats why you are getting this error. i succeed transferring my 2 application.
I've got a Meteor app hosted on Modulus. The app is an in-house app used by a few higher-ups in the company. We're giving it a first trial run. After deploying the app and the db to Modulus, I'm finding the data is reloading about every 10 seconds. It's like the data is reloading into minimongo, so same data appears to flash on and off. It doesn't do this running the app locally.
Insecure has been removed, but I left auto-publish in Meteor because the app needs the whole database to work with. I figured I could remove it and then publish and subscribe the whole database, but I thought that would be redundant. Could this be the problem?
I'm in contact the the Modulus folks about it, but I think they're scratching their heads. I've tried hosting the db on Compose as well with the same result. Something in the app is causing it. Was wondering if anyone might have a suggestion.
Autopublish is the culprit here. Try removing autopublish and convert your data access to publish and subscribe.
If you have already built the entire app, you will have to refactor the entire app as Thai Tran mentioned in the comments.
Also, even if you have every security in place where users are locked up, autopublish still messes your app's security up. Your entire database is on the browser. Even if you have users or not. (Not a best practice in a production app).
Meteor gives autopublish only for prototypes, not production apps.
Anyways, explanation here is with autopublish on there will be lot of Tracker incomputations which might cause these errors.
Remove it and your app should be fine (Of course after you refractor your app to use publish + subscribe).
Good Luck!