Post

Replies

Boosts

Views

Activity

Apple told us the issue was resolved, then asked us to resubmit anyway
This is the third time I've posted about our app, so apologies to anyone who's seen the other two threads (links at the bottom). I honestly don't know where else to ask. Our app is NotBetting (app ID 6737483983). Since August, every review has taken about eight days: August 14 to 22, September 4 to 12, and September 12 to 20. We've got used to that. What's getting to me is what happened after the last one. On September 20 we were rejected for two things. One was 3.1.1, because they thought a "Promo code" field at sign-up unlocked subscriptions. It doesn't. It's an affiliate referral code, it's only used for attribution, and it never unlocks or discounts anything. The label was confusing, I'll give them that. The other was 5.1.1(v): they said we make people register before buying In-App Purchases that "are not account based". We explained both in detail. We also asked one simple question: which of our products do you consider not account based? The account isn't a formality for us. People post content, report and block each other, and there's a public ranking, all tied to a member's identity. Apple got back to us within a day, which I really appreciated. They said, word for word, "The 3.1.1 rejection has currently been resolved", but that they "continued to find that the app requires users to register before purchasing In-App Purchases that are not account based." They didn't say which product. We asked again. The next reply, on September 22, was just: "We appreciate your efforts to comply with the App Review Guidelines. Please resubmit the app for review in App Store Connect once any necessary adjustments have been made." That was it. No guideline repeated, no answer to our question, nothing specific to fix. So we changed what we could guess at (full name is now optional on iOS, for example) and submitted a new version, 3.3.7, on September 23. Resubmitting closes the previous thread, and everything we'd explained goes with it. It's now been waiting for four days. If it follows the usual pattern, nobody will open it for another four. A couple of things that happened in the meantime make it harder to take: The TestFlight build of the same binary was rejected under 3.1.1 on the same day, with the generic text and no feature named. We asked which feature they meant. The next day it was approved, with no explanation either way. The same version was approved and live on Google Play within hours of us submitting it to Apple. And the version our iOS users can download from the App Store is still the one from late June. I'm not complaining about being rejected. If something's wrong, tell us and we'll fix it, usually the same day. What wears you down is the loop: one issue confirmed as resolved, another with no details, a "please resubmit" that doesn't say what to change, and the only way forward is another week in the queue. If anyone from Apple sees this, I'd really like to know three things. When a thread ends with "resubmit once any necessary adjustments have been made" and no issue is named, does that mean there's no remaining objection? How are we supposed to find out which product is "not account based" if asking in the Resolution Center doesn't get an answer? And is there any way to talk to someone before resubmitting, instead of after another week of waiting? Our request for an App Review appointment back in August was declined. If anyone else has been through this and found something that actually helped, I'd love to hear it. NotBetting, app ID 6737483983, version 3.3.7 (195), submitted September 23. Earlier threads: https://developer.apple.com/forums/thread/843019 https://developer.apple.com/forums/thread/845024
1
0
157
3w
Version stuck in "Waiting for Review" for 7 days - never moved to In Review
Hi, Our app update has been sitting in "Waiting for Review" for 7 days and has never transitioned to "In Review". App: NotBetting: Pronosticos Apple ID: 6737483983 Bundle ID: com.notbetting.mobile Version: 3.3.5 (build 193) Submitted: September 12, 2026, 15:49 UTC Current state: Waiting for Review (unchanged since submission) For context, our last released version on the App Store is 1.2.3, from June 24. Our users have been waiting a long time for this update, and the current delay is becoming a serious problem for us. Nothing was changed on our side after submitting, and the build is not a resubmission of a rejected binary. Is there anything we can check on our end, or any additional detail we can provide to help move this forward? I am happy to share a Case ID or anything else that helps. Thank you.
1
0
145
Sep ’26
Small Business Program: 3 weeks in, no answer, and the form now 500s
We applied to the Small Business Program on 14 August and got the "We've received your request" email at 01:36. Three weeks later, nothing. No approval, no rejection, nobody asking us for more information. If I try to apply again the form just returns a 500, which I take to mean the application is sitting open somewhere. What's bugging me is that the discount isn't retroactive — "your proceeds will be adjusted fifteen (15) days after the end of the fiscal calendar month in which your enrollment is approved". So every month that goes by is a month billed at 30% that we never get back, and there's nothing we can do from our side to speed it up. It's cost us something concrete too. We just submitted a new version with 122 in-app purchase products after a 3.1.1 rejection, and every one of those prices had to be worked out at 30% because we had no answer. Our iPhone customers are paying noticeably more than our web customers because of a form nobody has looked at. If it gets approved next month, we get to reprice all 122 of them. I've read here that people normally hear back in 6-10 days, and also that the "contact us" button on the program page lands on support who can't help because a different team handles the review. So has anyone actually got a stuck application moving? Did asking for a tier 2 advisor work, or a phone callback? Or is it just waiting?
1
0
379
Sep ’26
Nearly a month trying to get an update approved. We've missed our launch.
We were supposed to launch about a week ago. Today is September 8, and we're still trying to get our update onto the App Store. Honestly, it's exhausting. We're the team behind NotBetting (app ID 6737483983). The app has been on the store since December 2024, but the public version is still the one from late June. We've uploaded 32 builds in the last 30 days, including our ongoing development and beta testing. None of that work has reached users as a public App Store update. After moving the app to our company account on August 14, we waited eight days for a review. That review raised issues with moderation, age-rating metadata, permission wording and questions about our league. We made changes and resubmitted less than five hours after the rejection. Then we waited more than another week. The next rejection was for a black screen at startup. We investigated what happened when the connection failed and added a clear message and a retry button. We resubmitted just over two hours after the rejection. It took another four days for the next review. We later reported in our earlier forum thread that a subsequent build had been opened successfully. On September 3, the feedback was about In-App Purchase for tipster subscriptions. Apple had already raised that requirement in July. We've now rebuilt the purchase flow around StoreKit 2, and the current submission includes 122 IAP products. It has been waiting since September 4. That payment work has been a huge job for us. We're a marketplace: independent sports analysts sell access to their content and services, set their own prices, and receive an agreed share of each sale. We earn the platform's share. We have to account for Apple's commission, local taxes and currencies while still paying each provider correctly, including when a customer uses a discount. Then there are purchase verification, refunds and restoring access. We've also applied for Advanced Commerce API access because our catalogue changes all the time. Meanwhile, we keep finding and fixing other bugs. A lot can change in a week. The build sitting in the queue stays the same, so we have to keep it working with the backend while developing the next one. We've already had to fix a checkout compatibility problem without replacing the submitted build. Keeping older versions working is our job. We're doing it. But we're a small team maintaining the June release, the version waiting for review and newer builds at the same time. That takes time, and fixes that need an app update still can't reach our customers. Today our newer 3.3.4 build has gone into review for TestFlight, while the commercial 3.3.0 submission is still waiting. I understand those are separate reviews. It's still hard to watch testing move forward while the update our customers need sits there. The hardest part is having no date to work with. We can turn around a fix in hours, then spend days waiting for the next response. Our launch date has already passed. I can't tell people when we'll actually be ready on iOS. Our last successful submission in June went from submission to release in about 26 hours. This time we've spent weeks going through fixes and resubmissions. I'd really like to know whether our current submission is moving normally, or whether there's something we should be doing to get it unstuck. If someone from Apple can check, it's NotBetting, app ID 6737483983, version 3.3.0 (188), submitted September 4. And if you've been through this with your own app, what actually helped? We've already posted here before, and we're still trying to get this update out. Earlier thread: https://developer.apple.com/forums/thread/843019
0
0
104
Sep ’26
App stuck in "Waiting for Review" for 7+ days — anyone else since the Aug 8 maintenance?
Our update has been sitting in "Waiting for Review" since August 14, 2026 — over 7 days (171 hours as I write this). Details: iOS app, version 3.1.1, build 170 — build is VALID and correctly attached to the version Submission created, release type set to "after approval" No rejection, no Resolution Center message, no request for additional information Developer support case opened Aug 18 — still no reply The app was transferred to a new team (company account) on Aug 14, a few hours before the upload. The only warning we got was ITMS-90076 (keychain access change due to the new team ID), which is expected after a transfer and documented as non-blocking. Context that makes this painful: we have a commercial launch scheduled for September 1 that depends on this update, and the version currently live has bugs this release fixes. Questions for anyone in the same boat: Has anyone seen 7+ day waits specifically since the August 8 maintenance? Several threads here suggest a backlog. Did an app transfer right before the upload put your submission in a slower lane? That is the one thing that makes our case unusual. For those who eventually got through: what actually moved it — expedited review, a support case, or just time? (We already used an expedite earlier, so we would rather not burn another one.) Not looking to vent, just trying to figure out whether this is the general backlog or something specific to our submission that we could fix on our side.
13
1
646
Aug ’26
Apple told us the issue was resolved, then asked us to resubmit anyway
This is the third time I've posted about our app, so apologies to anyone who's seen the other two threads (links at the bottom). I honestly don't know where else to ask. Our app is NotBetting (app ID 6737483983). Since August, every review has taken about eight days: August 14 to 22, September 4 to 12, and September 12 to 20. We've got used to that. What's getting to me is what happened after the last one. On September 20 we were rejected for two things. One was 3.1.1, because they thought a "Promo code" field at sign-up unlocked subscriptions. It doesn't. It's an affiliate referral code, it's only used for attribution, and it never unlocks or discounts anything. The label was confusing, I'll give them that. The other was 5.1.1(v): they said we make people register before buying In-App Purchases that "are not account based". We explained both in detail. We also asked one simple question: which of our products do you consider not account based? The account isn't a formality for us. People post content, report and block each other, and there's a public ranking, all tied to a member's identity. Apple got back to us within a day, which I really appreciated. They said, word for word, "The 3.1.1 rejection has currently been resolved", but that they "continued to find that the app requires users to register before purchasing In-App Purchases that are not account based." They didn't say which product. We asked again. The next reply, on September 22, was just: "We appreciate your efforts to comply with the App Review Guidelines. Please resubmit the app for review in App Store Connect once any necessary adjustments have been made." That was it. No guideline repeated, no answer to our question, nothing specific to fix. So we changed what we could guess at (full name is now optional on iOS, for example) and submitted a new version, 3.3.7, on September 23. Resubmitting closes the previous thread, and everything we'd explained goes with it. It's now been waiting for four days. If it follows the usual pattern, nobody will open it for another four. A couple of things that happened in the meantime make it harder to take: The TestFlight build of the same binary was rejected under 3.1.1 on the same day, with the generic text and no feature named. We asked which feature they meant. The next day it was approved, with no explanation either way. The same version was approved and live on Google Play within hours of us submitting it to Apple. And the version our iOS users can download from the App Store is still the one from late June. I'm not complaining about being rejected. If something's wrong, tell us and we'll fix it, usually the same day. What wears you down is the loop: one issue confirmed as resolved, another with no details, a "please resubmit" that doesn't say what to change, and the only way forward is another week in the queue. If anyone from Apple sees this, I'd really like to know three things. When a thread ends with "resubmit once any necessary adjustments have been made" and no issue is named, does that mean there's no remaining objection? How are we supposed to find out which product is "not account based" if asking in the Resolution Center doesn't get an answer? And is there any way to talk to someone before resubmitting, instead of after another week of waiting? Our request for an App Review appointment back in August was declined. If anyone else has been through this and found something that actually helped, I'd love to hear it. NotBetting, app ID 6737483983, version 3.3.7 (195), submitted September 23. Earlier threads: https://developer.apple.com/forums/thread/843019 https://developer.apple.com/forums/thread/845024
Replies
1
Boosts
0
Views
157
Activity
3w
Version stuck in "Waiting for Review" for 7 days - never moved to In Review
Hi, Our app update has been sitting in "Waiting for Review" for 7 days and has never transitioned to "In Review". App: NotBetting: Pronosticos Apple ID: 6737483983 Bundle ID: com.notbetting.mobile Version: 3.3.5 (build 193) Submitted: September 12, 2026, 15:49 UTC Current state: Waiting for Review (unchanged since submission) For context, our last released version on the App Store is 1.2.3, from June 24. Our users have been waiting a long time for this update, and the current delay is becoming a serious problem for us. Nothing was changed on our side after submitting, and the build is not a resubmission of a rejected binary. Is there anything we can check on our end, or any additional detail we can provide to help move this forward? I am happy to share a Case ID or anything else that helps. Thank you.
Replies
1
Boosts
0
Views
145
Activity
Sep ’26
Small Business Program: 3 weeks in, no answer, and the form now 500s
We applied to the Small Business Program on 14 August and got the "We've received your request" email at 01:36. Three weeks later, nothing. No approval, no rejection, nobody asking us for more information. If I try to apply again the form just returns a 500, which I take to mean the application is sitting open somewhere. What's bugging me is that the discount isn't retroactive — "your proceeds will be adjusted fifteen (15) days after the end of the fiscal calendar month in which your enrollment is approved". So every month that goes by is a month billed at 30% that we never get back, and there's nothing we can do from our side to speed it up. It's cost us something concrete too. We just submitted a new version with 122 in-app purchase products after a 3.1.1 rejection, and every one of those prices had to be worked out at 30% because we had no answer. Our iPhone customers are paying noticeably more than our web customers because of a form nobody has looked at. If it gets approved next month, we get to reprice all 122 of them. I've read here that people normally hear back in 6-10 days, and also that the "contact us" button on the program page lands on support who can't help because a different team handles the review. So has anyone actually got a stuck application moving? Did asking for a tier 2 advisor work, or a phone callback? Or is it just waiting?
Replies
1
Boosts
0
Views
379
Activity
Sep ’26
Nearly a month trying to get an update approved. We've missed our launch.
We were supposed to launch about a week ago. Today is September 8, and we're still trying to get our update onto the App Store. Honestly, it's exhausting. We're the team behind NotBetting (app ID 6737483983). The app has been on the store since December 2024, but the public version is still the one from late June. We've uploaded 32 builds in the last 30 days, including our ongoing development and beta testing. None of that work has reached users as a public App Store update. After moving the app to our company account on August 14, we waited eight days for a review. That review raised issues with moderation, age-rating metadata, permission wording and questions about our league. We made changes and resubmitted less than five hours after the rejection. Then we waited more than another week. The next rejection was for a black screen at startup. We investigated what happened when the connection failed and added a clear message and a retry button. We resubmitted just over two hours after the rejection. It took another four days for the next review. We later reported in our earlier forum thread that a subsequent build had been opened successfully. On September 3, the feedback was about In-App Purchase for tipster subscriptions. Apple had already raised that requirement in July. We've now rebuilt the purchase flow around StoreKit 2, and the current submission includes 122 IAP products. It has been waiting since September 4. That payment work has been a huge job for us. We're a marketplace: independent sports analysts sell access to their content and services, set their own prices, and receive an agreed share of each sale. We earn the platform's share. We have to account for Apple's commission, local taxes and currencies while still paying each provider correctly, including when a customer uses a discount. Then there are purchase verification, refunds and restoring access. We've also applied for Advanced Commerce API access because our catalogue changes all the time. Meanwhile, we keep finding and fixing other bugs. A lot can change in a week. The build sitting in the queue stays the same, so we have to keep it working with the backend while developing the next one. We've already had to fix a checkout compatibility problem without replacing the submitted build. Keeping older versions working is our job. We're doing it. But we're a small team maintaining the June release, the version waiting for review and newer builds at the same time. That takes time, and fixes that need an app update still can't reach our customers. Today our newer 3.3.4 build has gone into review for TestFlight, while the commercial 3.3.0 submission is still waiting. I understand those are separate reviews. It's still hard to watch testing move forward while the update our customers need sits there. The hardest part is having no date to work with. We can turn around a fix in hours, then spend days waiting for the next response. Our launch date has already passed. I can't tell people when we'll actually be ready on iOS. Our last successful submission in June went from submission to release in about 26 hours. This time we've spent weeks going through fixes and resubmissions. I'd really like to know whether our current submission is moving normally, or whether there's something we should be doing to get it unstuck. If someone from Apple can check, it's NotBetting, app ID 6737483983, version 3.3.0 (188), submitted September 4. And if you've been through this with your own app, what actually helped? We've already posted here before, and we're still trying to get this update out. Earlier thread: https://developer.apple.com/forums/thread/843019
Replies
0
Boosts
0
Views
104
Activity
Sep ’26
App stuck in "Waiting for Review" for 7+ days — anyone else since the Aug 8 maintenance?
Our update has been sitting in "Waiting for Review" since August 14, 2026 — over 7 days (171 hours as I write this). Details: iOS app, version 3.1.1, build 170 — build is VALID and correctly attached to the version Submission created, release type set to "after approval" No rejection, no Resolution Center message, no request for additional information Developer support case opened Aug 18 — still no reply The app was transferred to a new team (company account) on Aug 14, a few hours before the upload. The only warning we got was ITMS-90076 (keychain access change due to the new team ID), which is expected after a transfer and documented as non-blocking. Context that makes this painful: we have a commercial launch scheduled for September 1 that depends on this update, and the version currently live has bugs this release fixes. Questions for anyone in the same boat: Has anyone seen 7+ day waits specifically since the August 8 maintenance? Several threads here suggest a backlog. Did an app transfer right before the upload put your submission in a slower lane? That is the one thing that makes our case unusual. For those who eventually got through: what actually moved it — expedited review, a support case, or just time? (We already used an expedite earlier, so we would rather not burn another one.) Not looking to vent, just trying to figure out whether this is the general backlog or something specific to our submission that we could fix on our side.
Replies
13
Boosts
1
Views
646
Activity
Aug ’26