Posts

Post not yet marked as solved
0 Replies
214 Views
Hi, is there a way to check programmatically if the App Store is disabled / enabled in MDM administrated environments? I've tried Storefront.current != nil (yes, I know it's async, this is just for easy understanding), however I am not sure as I cannot test this in an MDM environment right now.
Posted
by Uedich.
Last updated
.
Post not yet marked as solved
0 Replies
784 Views
Hi, a user sent me a crash report from an Mac that ran my app, which is running in "designed for iPad" mode there. Normally, my first step debugging this is to drag the .ips file onto Xcode, load the corresponding project and investigate the stack backtrace. However, in this case loading the symbols obviously fails (see attached screenshot, lines 3/4). How can I resymbolicate the backtrace in this case ("designed for iPad" app running on a Mac)?
Posted
by Uedich.
Last updated
.
Post not yet marked as solved
0 Replies
1.3k Views
In my app, I handle some files as UIDocuments. When the app is installed on an M-Mac (as "designed for iPad"), the corresponding file names show up in the recent files system menu. The problem is that these file are for internal use only - the users should not see their names (in fact, the file names are just UUID strings, which is quite confusing). Is there a way to prevent the Mac from listing the UIDocuments in the recent files menu? Or is there a way to clear the menu?
Posted
by Uedich.
Last updated
.
Post not yet marked as solved
0 Replies
399 Views
Since iOS 14, more and more users experience a severe problem: When they launch our app, it quits right after showing the launch screen, obviously even before executing one line of code. In some cases, offloading and re-loading the app can help in this situation, but not always. In iOS 13, the problem occurred in the same way, but offloading and re-loading always helped. This seems to be a licence problem and reinstalling is no option, because our app holds critical personal data that the user often did not backup. So what can we do in this situation?
Posted
by Uedich.
Last updated
.
Post not yet marked as solved
0 Replies
592 Views
Hi there,my app will soon switch to a newer version (from 6 to 7).Today, I have a release version of 6.1.27 (where .27 is the build number).In order to start the beta testing of 7.0, I would like to invite my testers via TestFlight, but still want to be able to release newer sub-versions of the current release, e.g. I want to keep the ability to release a version 6.1.28 while version 7.0.0 (or an alpha 6.9.x) is being tested already.How to I achieve that? Can I just upload a new build with a 7.0.x version number while the App Store will let me upload and release new versions with numbers lower than that?Thanks to all!
Posted
by Uedich.
Last updated
.