I have the same problem. Since iOS 14 it is not possible to create an album with PHAuthorizationStatusLimited.
I don't know how to explain this to users.
Post
Replies
Boosts
Views
Activity
Not yet.
Even after months the address has not been changed and there is no information. I also created a new account weeks ago with the new address in the new country and it is stuck in enrollment and was not activated.
Now the data of the developer account of my company has been updated. I just should have waited a bit.
Many thanks to the Apple team. Now we can concentrate on the development of new apps.
Unfortunately, our new app has now also been rejected twice. And is now probably waiting for the third rejection.
We have several apps where App Tracking Transparency authorization prompt has been showing successfully for a year on iOS 14 or newer. We always called it in viewDidLoad.
Now, the first time the new app was rejected because the App Tracking Transparency authorization prompt did not appear if called from viewDidLoad on iOS 15. That was our mistake because we unfortunately didn't test it on iOS 15.
When we submitted the app for the second time, we showed the App Tracking Transparency authorization prompt in viewDidAppear and tested it on an iOS 15 device. The App Tracking Transparency authorization prompt was displayed successfully. Unfortunately, the app was rejected for the second time with the same reason.
The third time we called the App Tracking Transparency authorization prompt from viewDidAppear after a 2 second delay.
Now the app has been waiting for review for a bit longer and we are afraid that it will be rejected again. It is really frustrating. It works with all our test devices and we don't get any more information from the review team.
Would it be possible that on the device of the review employee the "Settings -> Privacy -> Tracking" is disabled?
This is our code for the App Tracking Transparency request:
if (@available(iOS 14, *))
{
ATTrackingManagerAuthorizationStatus status = [ATTrackingManager trackingAuthorizationStatus];
if(status == ATTrackingManagerAuthorizationStatusNotDetermined)
{
[ATTrackingManager requestTrackingAuthorizationWithCompletionHandler:^(ATTrackingManagerAuthorizationStatus status)
{
// Tracking authorization completed. Start loading ads here.
[[NSOperationQueue mainQueue] addOperationWithBlock:^
{
[self loadBannerAd];
[self createAndLoadInterstitial];
}];
}];
}
else
{
[self loadBannerAd];
[self createAndLoadInterstitial];
}
}
else
{
// Fallback on earlier versions
}
Both times this was the reason for the rejection:
1.2 Legal: Privacy - Data Use and Sharing
Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing
The app privacy information you provided in App Store Connect indicates you collect data in order to track the user, including Advertising Data. However, you do not use App Tracking Transparency to request the user's permission before tracking their activity.
Starting with iOS 14.5, apps on the App Store need to receive the user’s permission through the AppTrackingTransparency framework before collecting data used to track them. This requirement protects the privacy of App Store users.
Next Steps
Here are two ways to resolve this issue:
If you do not currently track, or decide to stop tracking, update your app privacy information in App Store Connect. You must have the Account Holder or Admin role to update app privacy information.
If you track users, you must implement App Tracking Transparency and request permission before collecting data used to track. When you resubmit, indicate in the Review Notes where the permission request is located.
The app has now been accepted with the 2 seconds delayed call.
But since a delay is not a best solution, we have now solved it differently.
As before, we now call a method from viewDidLoad without delay.
In this method we check the status of the application. If the status is not active, then we call this method recursively after 0.5 seconds. As soon as the status is active, we call App Tracking Transparency authorization prompt.
It should work that way and get through the review without any problems. We'll try to submit an update tomorrow.
-(void)initAds
{
UIApplication *applicaiton = [UIApplication sharedApplication];
if (applicaiton.applicationState == UIApplicationStateActive)
{
if (@available(iOS 14, *))
{
ATTrackingManagerAuthorizationStatus status = [ATTrackingManager trackingAuthorizationStatus];
if(status == ATTrackingManagerAuthorizationStatusNotDetermined)
{
[ATTrackingManager requestTrackingAuthorizationWithCompletionHandler:^(ATTrackingManagerAuthorizationStatus status)
{
// Tracking authorization completed. Start loading ads here.
[[NSOperationQueue mainQueue] addOperationWithBlock:^
{
[self loadBannerAd];
[self createAndLoadInterstitial];
}];
}];
}
else
{
[self loadBannerAd];
[self createAndLoadInterstitial];
}
}
else
{
// Fallback on earlier versions
}
}
else
{
[self performSelector:@selector(initAds)
withObject:nil
afterDelay:0.5f];
}
}
We have the same problem now. Was someone able to solve the problem via email with the Apple team? How long did it take?
We accepted the new agreement on December 14th. Unfortunately, the App Store Connect system did not notice this. Now it is not possible to update the apps.
We have the same problem now. Was someone able to solve the problem via email with the Apple team? How long did it take?
We accepted the new agreement on December 14th. Unfortunately, the
App Store Connect system did not notice this. Now it is not possible to
update the apps.
We have the same problem now. Was someone able to solve the problem via email with the Apple team? How long did it take? The German support doesn’t understand the issue. Is there a direct email address for US support?
We accepted the new agreement on December 14th. Unfortunately, the App Store Connect system did not notice this. Now it is not possible to update the apps.
Unfortunately, we also received a standard response from support: "You have to accept the agreement." But there is nothing to accept. The users are still waiting for the apps to be updated. There is no solution in sight.
The second Apple employee was able to help me via email. I was able to agree to the agreement and update the app. It took two days with the email support. In the time of the holidays it is a good response time in my opinion. Thanks to the Apple team for the quick help.
The second Apple employee was able to help me via email. I was able to agree to the agreement and update the app. It took two days with the email support. In the time of the holidays it is a good response time in my opinion. Thanks to the Apple team for the quick help.
The second Apple employee was able to help me via email. I was able to agree to the agreement and update the app. It took two days with the email support. In the time of the holidays it is a good response time in my opinion. Thanks to the Apple team for the quick help.
We also have this problem with all our apps since iOS 15. Before that, the pictures were saved in the album for years without any problems. This only happens on some of my users' devices. We could not reproduce the problem on our test devices. Unfortunately, we can't fix this issue.
We also have this problem (PHPhotosErrorDomain error 3300) with all our apps since iOS 15. Before that, the pictures were saved in the album for years without any problems. This only happens on some of my users' devices. We could not reproduce the problem on our test devices. Unfortunately, we can't fix this issue.