- #DIFFERENCE BETWEEN IEXPLORER AND IBROWSE INSTALL#
- #DIFFERENCE BETWEEN IEXPLORER AND IBROWSE DOWNLOAD#
The process of re-signing the AppManager mobile app is described in this article. This makes the AppManager mobile app signed with your identity and distribution method and is subject to the same troubleshooting specifics. Instead, we distribute it over-the-air and require you to re-sign it with your certificate and provisioning profile.
Delete all files in “Media > Downloads”ĭue to some specific limitations, we can't distribute the AppManager mobile app through the public App Store.
#DIFFERENCE BETWEEN IEXPLORER AND IBROWSE DOWNLOAD#
Download iExplorer () or its free version iBrowse () on your Mac.It's not user friendly and you need a Mac, but you can still try it out: There is one unofficial way to "free" the cache. There is still a chance that iOS cached something and ignores the app install. Of course, if your other users are using different networks and still cannot download the app, it means this is not relevant.Ģ. There is a slim chance your network is blocking the app download somehow. Try installing the app from another network. There are a couple of other things that you can try.ġ. Sending us this error log would greatly help us understand what exactly is happening on your end. Once the console is opened, try installing the app and see the error log that the iOS reports. There is a small triangle on the bottom of the window that opens the console. If you have a Mac, you can connect your device, open XCode and go to Window -> Devices.
#DIFFERENCE BETWEEN IEXPLORER AND IBROWSE INSTALL#
The only way of investigating this problem would be to connect a device to a Mac and get the error logs while you try to install the app and it fails. Can you please clarify if this happens only on your device or on all of the devices of your users? Also, what versions of iOS are you trying to install the app on? Perhaps, in your case there is something more. In such cases a completely new App Id and provisioning profile fixes the issue. Normally, such errors are caused by the iOS caching app ids that it decided are not good for some reason.
0 kommentar(er)
