Does anyone know what causes this? I get this each time I try to make a Distribution provisioning profile, and on both my Apple Developer Accounts. Can anybody tell me what I do wrong or is this a error caused by Apple.
We are unable to process your request.
Please go back to the previous page,
or quit your browser and try your
request again. If you require
assistance, please contact Apple
Developer Support.
Same issue here. I've called Apple Developer Support in Canada and their rep is now researching the issue and should update me within the hour. I'll post what he says here.
UPDATE
Turns out, Apple is experiencing unusually high server loads due to yesterday's keynote rekindling interest in iOS development. Try again outside peak traffic hours.
Related
App is built in flutter using Firebase authentication. When Apple review team tries to sign in by using provided testing phone number and they always stuck at reCaptcha based authentication screen. They are seeing attached screen forever.
App store rejected by giving reason:
Hello,
The issues we previously identified still need your attention.
If you have any questions, we are here to help. Reply to this message
in App Store Connect and let us know.
Guideline 2.1 - Performance - App Completeness
We discovered one or more bugs in your app.
Specifically, your app still displayed error message when we tried to
login.
Please review the details below and complete the next steps.
Review device details:
Device type: iPhone
OS version: iOS 15.5
Next Steps
Please run your app on a device to reproduce the issues, then revise
and submit your app for review. If at first you're unable to reproduce
the issue, try the following:
For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce.
For app updates, install the new version as an update to the previous version, then follow the steps to reproduce.
If we misunderstood the intended behavior of your app, please reply to
this message in App Store Connect to provide information on how these
features were intended to work.
Resources
For information about testing apps and preparing them for review, see Technical Note TN2431: App Testing Guide.
To learn about troubleshooting networking issues, see About Networking.
Please see attached screenshot for details.
Issue faced by Apple Review Team
I have tried following things:
https://firebase.google.com/docs/auth/ios/phone-auth#set-up-recaptcha-verification - As per this link i have done same configuration in Xcode, Put my REVERSED_CLIENT_ID in the URL schemes,
iOS URL Scheme in xCode
Also I have done APNs authentication key at firebase side,
Firebase APNS Configuration
However, I am unable to reproduce this issue at my end. But though, I tried all the possible solution based on answers on the SO. Still issue doesn't resolved for them.
Please let me know if am I missing some configuration?
Have you tried this?
Go to your firebase Project settings => App Check => Apps
Register your apps for app attention.
I have tested all my IAP product in the sandbox environment, but after the app been approved by Apple's review team, it just do not work:
I downloaded and installed my app from the appstore, when I pressed the product, my app tried to fetch the product's information using the "product id" but got 0 result.
Then I deleted the app, and installed it using the Xcode, and the app worked pretty well, as you know, at this time it connected to the andbox.itunes.apple.com environment.
Does anyone have met such a problem? Can you help me please?
I'm experiencing exactly same issue right now. Having in mind you are asking same question 15 mins earlier than me, I may suggest this is something going weird on Apple's servers. I have googled this and looked for the similar questions here, and it appears that it takes some time before IAP are available. So I dropped message to Apple support, but I guess we need just wait some time.
Anybody met such a problem just have to wait for 2 days, be patient, this is an issue of Apple itself!
After making an update to an iPad app I released some time ago, I've been getting reports that people are unable to actually update the app without deleting and re-installing. However, as far as I know, nothing in the update should be causing this. (All the update deals with is letting people email PDF documents, nothing major.) When people attempt to update, they're asked for their iTunes password, but after entering it, it merely goes back to the update screen and nothing happens. Additionally, it would seem that this only happens with my app, the people in question aren't having any issues with the other various apps on the App Store. Does anyone know what might be causing this and how I could fix it?
Thanks in advance!
(Also, if it matters, the app is a custom B2B app, the general public can't purchase it.)
I'm removing the text of my answer because it's so inaccurate it's embarrassing. I mistook "B2B" for "Enterprise" and answered based off of that. To make up for it, I'll look into the problem a bit more and if I find anything I will edit this answer accordingly.
Edit:
Okay, I can see why you put a bounty for this question on SO; there's not really any data on a problem like this anywhere. Frankly, there's not much available information on B2B in general. I'll post what I found anyway, in case it can be of any help to you.
I found the details reason behind Maggie's question, there. Per Editing and Updating App Information:
Updates keep the same Apple ID and bundle ID, which means they are
associated with your first version and free to your customers
Also, apparently, "You can't change the CFBundleIdentifier of a released app if you want to release updates for it, the App Store will automatically reject it when you upload." which is something I can vouch for, having experienced this with a normal app. I do know that for a B2B app you do have to submit it to Apple for review, but I can't tell from the documentation I found if you need to actually submit it to the App Store, so it may not go through the various checks that normal apps go through, so this could be your problem.
Aside from that, according to the VPP guide, if your customers are installing the apps on the devices with Apple Configurator (broken right now, per app store reviews) the updates also have to be done with the Configurator. You haven't said that Configurator was involved, but I did find this tidbit.
• Use Apple Configurator to install apps on new or supervised devices.
Apple Configurator on a Mac makes it easy to mass configure and deploy
devices that are centrally controlled. Redemption code spreadsheets
acquired through the Volume Purchase Program can be imported by Apple
Configurator, tracking the number of apps installed on each device. To
update deployed apps using Apple Configurator, you must reconnect to
the same Mac from which the apps were installed. Learn more at
itunes.apple.com/us/app/apple-configurator
Anyway, good luck. Wish I could be more help.
What you are describing (assuming that it is accurate) would certainly be a bug on Apple's side. If users are trying to update the app and the update is not being processed, then in one way or another that is a bug that Apple needs to address. Nothing that you do as a developer should be able to cause that situation to happen. I would suggest contacting Apple and possibly filing a bug report.
It seems that apple wants you to develop the Iphone apps in the latest build. Sometimes this cause issues between realeases (diferent versions of Itunes, OSX, IOS, etc) when you try to update your apps.
Try to publish the app in the latest version of xcode.
That happens a lot in iphone development testing.
Hope this help.
When updating an app, iOS looks for the bundleId and if there is another app with the same bundleId, it updates the app with the highest version number. Maybe the version number is not set correctly or maybe people have issues because an other app (from the AppStore or an other B2B app) have the same bundleID but a higher version number.
I'm by far not an iPhone expert, but it seems something related might have been fixed in iOS 6.0.1.
Fixes a bug that prevents iPhone 5 from installing software updates
wirelessly over the air
We recently launched an update to an iPhone application. While our push notifications were working perfectly in ad-hoc, we've moved to live and they are no longer registering.
Looking at a live device log, we're seeing this:
"Jun 11 09:40:05 unknown SpringBoard[5791] : No valid 'aps-environment' entitlement string found for application 'App Name': (null). Notifications will not be delivered."
Now if you check on the internet or other stack-overflow conversations, there is a very common answer to this that the provisioning profile did not have "aps-environment" set as "production" correctly and the profile needs regenerating. However, this does not appear to be our issue as the binary clearly indicates it is in production aps environment. See details from the App Store Binary Details below:
So we are a bit lost for what the problem could be. Given this information, as well as numerous checks I have done on my side, the profile and code signing appear to be correct and I can't find any other solutions to this online at the moment.
Thanks in advance for your help.
So this problem worked itself out in the span of 3 hours; it must have been a server propagations issue.
To anyone who might pull their hair out in the future on this one: If your app JUST went live and the notifications aren't registering and you are certain that the aps-environment is set correctly, wait a few hours prior to concluding that the app has an issue.
Our app was launched in the Canadian iTunes Store only and the push notification registration issue resolved itself within a 3 hour period.
If anyone in the future can explain why this happens or add more detail to this, I'll gladly accept their answer.
I found this information on a blog which talks about invalid product ids.
http://troybrant.net/blog/2010/01/invalid-product-ids/
I tried everything suggested in the
Apple forums and here, and still
couldn’t get it to work. Found the
solution – your app needs to be
transferred by Xcode for the sandbox
to be enabled.
Obvious, right? Well, if you are
working with an update to an existing
account, the device will still treat
it as an App Store-installed app.
Delete it, then transfer it again. It should work now :)
i am also getting invalid product ids.i am not able to get clear in the above said point...
i am not able to understand what i need to do when transferring the application into device...
Kindly guide me out and thanks for your help
That point just means that you need to run the app from Xcode in order for the sandbox to be available. (Build and Run)
Invalid product ids are a major pain to debug. If you're sure you've gotten everything on that checklist, then you just need to wait. Then only other problem that I've seen is that you might need to remove the app from the device and redeploy in order to get good products back from the store.
I had trouble getting the app store to recognize my sandbox test account. I had to log out wit iTunes, sync, then log in again with iTunes. Just using the device itself to log in/out didn't help.