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
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'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)
I am testing WSO2-Emm system for managing our android mobile app. We have an app for taxi drivers. We deploy it using our tablets and a single gmail account. Our problem is that google allows up to 10 signed in devices for a single google account.
I have tried to load the apk to the WSO2 store. The problem is that when I want to upload a new version of the same app I get a warning message saying that this APK already exists in the store. When I try to rename it and add it as a new apk it works. The problem is that when I go to App-Management, the application appears under 'installed'. The Emm system doesn't detect there is a new version.
To be more specific, my question is is there a way to manage mobile application versions using the WSO2 store and not the google play store.
If there is a way we can go on with this system. If not, we will stop testing it.
The only way I've figured out how update an already installed app is by going to the App Management tab, selecting your latest version of the app in question, and hitting the install button under the Roles tab (NOT the Users tab). It will send the install command to any devices listed under roles you have checked, even if they already have the app installed. Keep in mind this will install the app on all the devices, even devices that already have the version you're trying to put out.
It looks like you already know about the patch on EMM-686 that must be implemented in order to upload multiple versions of the same app to the Publisher. Just in case you want to confirm it's implemented correctly, see my answer here for instructions on how to implement it.
I'm about to implement some unlock-functionality In-App-Purchase in an app. The client would like the functionality to be available the first two weeks after installing the app, and then go away until the user pays up.
I need the app to determine whether it has been previously installed, deleted, and installed again. If I can't do that users can just reinstall the app and get two more weeks for free.
Any ideas?
It seems all data is deleted when the app itself is deleted, which kind of limits my options. There is a server backend to the app. Is my best option to log something there or is there another way?
You can make use of the keychain in iOS. It will not be removed even if you uninstall the app. But you have to make sure you use the same provisioning profile across different versions of your application.
And, have a look at this utility
I have posted this on the Apple support site but just seeing whether anyone can be of benefit here. We have a business iPad app which has been deployed to our users using the ad-hoc distribution method for trial purposes.
Their iPads are backed up using the iCloud automatic method and from what I gather our ad-hoc app (and data) is backed up using this method. Recently a user has deleted the app.
As part of the "Restore from Backup" process, all the AppStore apps are downloaded and installed as per normal, but with the ad-hoc apps they arnt restored at all. It just shows "Waiting ... and then Installing ..." and then it disappears. Im guessing its related to the fact the iPad cant redownloaded an ad-hoc app (it doesnt know where it came from), but how do we update the ad-hoc app on that device after a iPad Restore is done ?
Is there any way to get back the ad-hoc app and its data ?
Thanks for any advice.