I'm not getting any crash report data on the application dashboard for an app that I had previously setup and configured on a different organization account. I'm able to upload and distribute builds but the crash report data goes to the previous account's dashboard. I thought deleting the app from the previous account dashboard would fix the issue but after deleting the app I'm not getting crash report data in either account now. I don't want to loose the uploaded builds or release history otherwise I would have tried deleting the app from both places and trying to configure it again from the account where I want to distribute builds and receive crash data.
Thanks for reaching out. It sounds like the old organizations API keys are still cached in your app. Please clean your app and check the info.plist and run script build phase (or if Android, AndroidManifest and/or fabric.properties file)
Related
It is possible to update the current app from Appstore and GooglePlay from a new freshly expo project?
I lost all the code of the project from where app was build(the build was classic one)
Now I want to start a new / fresh expo project(EAS one) and:
Code the app again
Update the stores with new app
What's your thoughts about this?
What about the implications of the parts like: Storages, Tokens..?
Thank you
As long as you have access to the same AppStore and Google Play accounts yes, you could. Without referencing legacy code and configuration, however, it might not be possible to migrate user data persisted in storage etc. (unless you know the exact config used).
The differences between classic expo builds and EAS should not have any impact here. What matters is that the apps have the same bundle id / package name and are correctly signed (you must have access to the previous signing key or publish key for google play, for instance), and that all other native config items match (if the previous app supported iPads, for example, the new one must as well).
I have developed an Android app using react native.
When I run on simulator its fine, and also when I debug via USB on real device its fine.
However when I publish to Google Play store and download the app as a regular customer it sometimes crashes.
Are there any logs somewhere that I can refer to in order to identify what the issue is? Or perhaps there is something I can add to code to help identify where/why issue is occuring.
You can use log errors to do so, record the activity of user. When the app crashes, your app can ask the user to send the bug report.
Using that bug report you can understand why your app crashes.
You could also use tools like Sentry or Firebase Crashlytics with an Error Boundary
wrapping your app to report errors, allowing you to have a better understanding of the production errors by displaying the full error stack trace and a lot more.
New builds get uploaded to fabric. I have one-two groups with multiple users in fabric attached to the project. They are not receiving notifications on their test devices with every builds but sporadically. They can download the builds manually through the app, but the emails are not consistent with releases in beta. What does that depend on?
We have some legacy apps on the Fabric dashboard though not sure if we'd ever needed them again so we could delete them from the dashboard.
If we do republish them, can we undelete them later?
If not, could we get another Fabric key to republish them with?
If you re-onboard the deleted app, by installing one of the kits, and building and running your app, it will re-appear on your Fabric dashboard. The historical data won't be available though. If you recently deleted an app by accident and need to restore the original app and data, we can help you out at support#fabric.io
I am working on developing a Mac application that has an in app purchase. I have done this before on iOS, but I cannot get it to work with the Mac app. After doing some research it looks like I will have to get and validate a receipt from the Mac App Store before this will work.
I believe that I have followed the steps to do this correctly,
1.) Build the app in Xcode.
2.) Launch the app through finder
3.) When prompted sign in with a TestUser account created in iTunesConnect
4.) The app closes with the error message
“AppName” is damaged and can’t be opened. Delete “AppName” and download it again from the App Store.
When I open up the bundle though I do not see the _MASReceipt/receipt folder and file - and I am still getting invalid product identifiers from StoreKit.
These steps seems to work for me the last time this happened:
Log out from Mac App Store.
Force quit storeagent and softwareupdated processes.
Try double-clicking the app to start it again.