Post marked as unsolved
606
Views
I'm testing my MAS app using Sandbox Test accounts - when I start the app I get the sign-in dialogue with the Apple ID field filled in with a previous account, and ready for password entry. However I want to change the Apple ID to use a different account but it won't open that field to edit.I'm sure this has been possible in the past - but now it is just frustrating - there doesn't seem to be a way to escape out of the pre-populated Apple ID.
Post marked as unsolved
260
Views
I have an app that is currently in the Mac App Store. It consists of the main app, and a bundle in the PlugIns folder (/Contents/PlugIns) as well as a Luncher helper /Contents/Library/LoginItems/
With Xcode 12.4 I am able to build but when I upload it to Apple I get a error:
ERROR ITMS-90296: "App sandbox not enabled. The following executables must include the "com.apple.security.app-sandbox" entitlement with a Boolean value of true in the entitlements property list: [( "com.xericdesign.earthdesk.mas.pkg/Payload/EarthDesk.app/Contents/Library/LoginItems/EarthDesk Launcher.app/Contents/MacOS/EarthDesk Launcher" )] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app."
The sandbox IS enabled for the Launcher.
This is very frustrating.
Post marked as unsolved
129
Views
Hello (from France),
Since Big Sur, all the usual apps in the Finance category are gone, including mine.
In this situation, no apps can be purchased and my income drops to zero.
To me this is more than a bug because some money is involved and it looks like a non respected contract on the Apple side since Apple have to show apps on the Mac App Store so they can be purchased .
Am I missing something?
Best regards.
Post marked as solved
194
Views
Hi Everyone,
After my submission to the Mac App store was rejected upon review, I was advised to test the application in a minimally privileged environment (because I could not otherwise reproduce the reported error). According to the documentation archives, one way of achieving this is by testing with a Guest Account.
Unfortunately I am only able to access safari through the Guest Account, so I do not see how I am able to test a MacOS app in this manner. After some searching on the web, I could not find a solution to my query. I wonder if I am asking the wrong questions?
As you might be able to tell from this post, I am very new to macOS App development, so please bear with me here.
Any help is greatly appreciated - thanks in advance!
D.
Post marked as unsolved
223
Views
My app has a helper application to register with launched using-
SMLoginItemSetEnabled
When both the main app and helper app are signed with dev cert, the helper app is launched/called as soon as you login, but a prod singed apps do not work as expected. In this case, the helper app is not auto launchd upon login.
This behavior is not seen in macOS 11.0/11.1. Here the prod signed helper app is launched as expected upon login.
Upon further investigation, I found the following log entries in system.log file
Feb 11 00:38:33 MacBook-Pro com.apple.xpc.launchd[1] (com.company.HelperApp[2121]): LaunchServices returned a bundle URL that does not match with the LoginItem's known association.
Feb 11 00:38:33 MacBook-Pro com.apple.xpc.launchd[1] (com.company.HelperApp[2121]): Service exited with abnormal code: 78
Feb 11 00:38:33 MacBook-Pro com.apple.xpc.launchd[1] (com.company.HelperApp): Service only ran for 0 seconds. Pushing respawn out by 10 seconds. What does the log mean and how can I get the prod signed builds to work as expected?
Post marked as solved
175
Views
Hi Everyone,
After my submission to the Mac App store was rejected upon review, I was advised to test the application in a minimally privileged environment (because I could not otherwise reproduce the reported error). According to the documentation archives, one way of achieving this is by testing with a Guest Account.
Unfortunately I am only able to access safari through the Guest Account, so I do not see how I am able to test a MacOS app in this manner. After some searching on the web, I could not find a solution to my query. I wonder if I am asking the wrong questions?
As you might be able to tell from this post, I am very new to macOS App development, so please bear with me here.
Any help is greatly appreciated - thanks in advance!
D.
Post marked as solved
164
Views
Hi Everyone,
After my submission to the Mac App store was rejected upon review, I was advised to test the application in a minimally privileged environment (because I could not otherwise reproduce the reported error). According to the documentation archives, one way of achieving this is by testing with a Guest Account.
Unfortunately I am only able to access safari through the Guest Account, so I do not see how I am able to test a MacOS app in this manner. After some searching on the web, I could not find a solution to my query. I wonder if I am asking the wrong questions?
As you might be able to tell from this post, I am very new to macOS App development, so please bear with me here.
Any help is greatly appreciated - thanks in advance!
D.
Post marked as unsolved
130
Views
does anyone know if the mac app store ranking system has changed recently for mac apps? my mac apps have dropped like a proverbial rock in the ranking system near the end of last week. has any one done any experiments to see if mac app store rankings are higher if you recompile your apps for M1 apple silicon systems?
Post marked as unsolved
460
Views
I created a macOS project using XCode 11.5 on macOS 10.15.5. Before that I created an App Store app record with macOS support.
When I archive this app and validate it the validation fails with messages:
App Store Connect Operation Error
Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, key 'com.apple.security.files.user-selected.read-only' in 'io.my.My.pkg/Payload/My.app/Contents/MacOS/My' is not supported. App Store Connect Operation Error
Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, key 'com.apple.security.app-sandbox' in 'io.my.My.pkg/Payload/My.app/Contents/MacOS/My' is not supported. Here is the entitlements:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>com.apple.security.app-sandbox</key>
<true/>
<key>com.apple.security.files.user-selected.read-only</key>
<true/>
</dict>
</plist>
I can not find any information about this issue and since the App Store is required the app sandbox I also can not turn it off.
Post marked as unsolved
98
Views
Hi,
I have early 2015 Macbook Pro laptop.
I installed Big Sur 11.2 today. Even before that Mac OS was not allowing me to install Xcode.
Now which version should I downgrade to so it works I can start coding again in Xcode.
Or any alternate way to start and enable myself to use Xcode 12 somehow please help
Error : we could not complete purchase. Not enough space on disk
.
Disk has 40 GB space empty
Xcode needs 12 GB
Post marked as unsolved
94
Views
Can't install garageBand using AppStore on Mojave 10.14.6. Apple support says I have to upgrade to Big Sur to use GarageBand which is unacceptable for me.
It seems strange to me. Mojave is still supported, there was a version of GarageBand that used to work with it. I can't believe GarageBand developers deleted older versions from their private repositories. Is there a chance I can get a Mojave compatible version of GarageBand?
Post marked as unsolved
132
Views
I'll keep it short
My app got rejected
Reason was app crash, on checking error code it looks like code signing issue
I had done the best by following the code signing documentation, testing it locally and using transporter to verify the package
Now I'm not sure if this is a bug in OS or code signing or something is missing in the documentation.
I have raised request to support. They shared documentation link with me again. I raised code-level support, no response.
Should I give up to publish on macOS store or there is any hope?
Post marked as unsolved
159
Views
Hello,
I've been battling an issue with my sandboxed app for a long time and I would really appreciate any help on the matter as I'm out of ideas.
My app uses USB detection to detect if a usb device or camera has been connected so I can read video files from it and present them to user within the app.
My problem is I can't get the USB detection to work in any way within the sandboxed app (works fine without sandbox entitlement)
Things I've tried:
Signing the sandboxed app with the usb entitlement and many others, nothing seems to work.
Giving the app Full Disk Access and External Volume Access.
When I look for my app in the console I see that the Sandbox blocks the read-write request when I connect a USB device, so it is a matter of permission rather than bad code or something.
Any help would be greatly appreciated as I am at a dead end and we can't release our App like this.
Thanks!
Post marked as unsolved
299
Views
Hi,
We have an Mac Catalyst universal bundle app which support multiple languages(French,Spanish,German etc). But the languages are not getting displayed in Mac AppStore, only English is displayed under languages.
The related iOS app (same bundle id) showing all supported languages in AppStore. The supported languages are available in Mac system preferences under my app language settings.
We have also added the supported languages under app store connect localization
is there anything specific we need to do, to show all supported languages in mac appstore for universal bundle app?
Post marked as unsolved
160
Views
After switching to BigSur and a MacBook Air with M1 I am not able to validate or distribute my archived app that contains a QuickLook Plugin generator for my own file format.
Xcode 12.3 crashes during validation process.
If I remove the QuickLook generator from my app bundle everything works fine. A fresh rebuild of the generator on my Apple Silicon Macbook air did not help.
On my older MacBook Pro running Catalina and Xcode 12.2 validation and distribution are successful.
I suspect some kind of signing problem but automatic signing is activated.
I've already integrated the new QuickLook extension API but would like to keep the old generator to support older macOS versions.
What am I doing wrong?