Search results for

“apple pencil battery life”

152,365 results found

Post

Replies

Boosts

Views

Activity

Reply to App rejected under Guideline 2.1(a) - App Completeness. Seeking advice!
If your app has been rejected and you need help resolving the issue, consider taking advantage of one of the following support options available from App Review: Reply to the message from App Review in App Store Connect and request clarification. Request a call with an Apple representative to discuss the outcome of the review. Submit an appeal to the App Review Board if you believe your app follows the App Review Guidelines. Visit the Contact Us page on Apple Developer and select the App Review tile to learn more.
1w
No contact from Support and No Review (5 Months Now)
My investors are losing their minds. We’ve had our app available on Google since late December, but our experience with Apple has been a nightmare. First, despite paying the developer fee, nobody responds to emails or reaches out. The one time we got Apple on the phone, we spoke to someone who said she was in charge of the testing team reviewing our app. The call was frustrating—she didn’t seem familiar with basic app testing for a location-based product (for example, how to emulate a different location), and it left us feeling helpless. The technical ability of the testing process has been shocking. We spent a month just trying to get reviewers to understand the basic app concepts. Our app also isn’t available in the United States, which seemed to confuse the review team. We’ve been able to address feedback quickly—sometimes within an hour—yet here we are nearly five months later still stuck. Right now we are averaging about a week at best to two weeks. Our app works; we know this because i
7
0
321
1w
App Stuck in “In Review'' status
Hi everyone, My app has been stuck in In Review status for over 20 days with no updates. I submitted the app on March 1, 2026, the status changed to In Review on March 4, 2026, and after that no changes. App ID: 6755649144 I also reached out to Apple Developer Support on March 15 but haven't received any response. Support Case ID: 102845096494 Could someone from App Review please take a look? Also any advice on how to move things forward would be appreciated. Thank you!
1
0
62
1w
TestFlight In-App Purchase (Consumable) gets stuck when using real Apple ID – cannot repurchase even after finishTransaction
**Environment Platform:** iOS Distribution: TestFlight Product type: Consumable In-App Purchase Account used for testing: Real Apple ID (not Sandbox) StoreKit: StoreKit 1 iOS version: iOS 17+ (also reproduced on earlier versions) Issue Description We are encountering an issue when testing consumable in-app purchases in a TestFlight build using a real Apple ID. Under normal circumstances, consumable products should be purchasable repeatedly. However, in TestFlight, after a successful purchase flow, the same product may become unavailable for repurchase, and the transaction appears to be stuck, even though: • finishTransaction: is correctly called • The transaction state is .purchased • No pending transactions are left in the payment queue Once this happens, subsequent purchase attempts result in behavior similar to a non-consumable product (e.g. “already purchased” or no purchase UI shown).
4
0
246
1w
Reply to Rejected a couple of time for 5.1.1/5.1.2 - AI consent screen not seen by reviewers despite being first screen on launch
Thank you for the feedback. Let me clarify: My app is a SwiftUI iOS fitness app called GymFusion. It uses Anthropic's Claude AI API to power features like meal photo scanning, body composition analysis, and workout coaching. The rejection is solely about Guidelines 5.1.1(i) and 5.1.2(i) — the app shares user data with a third-party AI service (Anthropic) and Apple says the app doesn't clearly disclose this or ask for permission. There are no in-app purchase issues — apologies for any confusion. Here's what I've implemented: The app's entry point (RootView) shows the AI consent screen as the first view on every launch. It's not a sheet or popup — it's embedded in the view hierarchy: if auth.isLoading { // Loading screen } else if !consentManager.hasConsented && !consentManager.hasSeenConsent { AIConsentView() // Consent blocks the entire app } else if auth.isAuthenticated { MainTabView() } else { AuthView() } The consent screen: Lists all data shared (photos, workout history, body measurements
1w
Reply to Universal Links and Cloud-testing platforms
Hi, Thank you again for your continued guidance on this. Since Universal Links are part of our sign-in/login/authorization workflow, they are required for all of our testing workflows. Our cloud testing platform has indicated that if we distribute the app to them via the Apple Developer Enterprise Program, they would not need to re-sign it, which would preserve the Associated Domains entitlement and allow the sign-in flow to work correctly on their device farm. Since our app also needs to be published to the App Store, we would continue using our standard Apple Developer Program for that purpose. Is this a valid scenario? We want to stay within Apple's supported provisioning model. If maintaining both an Enterprise Program and a Developer Program membership is the right path forward, we are prepared to do that.
Topic: Code Signing SubTopic: Entitlements Tags:
1w
Reply to FSKit passthrough sample fails to mount
[quote='881252022, alexfs123, /thread/819160?answerId=881252022#881252022, /profile/alexfs123'] I got a couple of kernel panics while developing a new plugin. [/quote] Kernel panics are always bugworthy. See Bug Reporting: How and Why? for my advice on how to file effective bug reports. And please post your bug number, just for the record. Honestly, I’d be surprised if these kernel panics were caused by FSKit. My experience is that kernel panics are usually caused by other subsystems within the kernel. However, the only way to know for sure is to get a bug on file. As to the behaviour of PassthroughFileSystem, keep in mind that it’s sample code, not a production file system. If you encounter weird problems, it’s worth investigating whether those issues are caused by FSKit or by the sample. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Core OS Tags:
1w
Reply to App Review Inefficiency
I'm in the middle of the same nightmare. Multiple rejections with no helpful information - very vague. No specifics that would allow me to make the required changes and resubmit. Filed an appeal, which was rejected. Set up a call, was told 3-5 business days, then on business day 4 was told another 3-5 business days. So disappointed in Apple. Can anyone tell me exactly what I need to do to pass review so I can do it and get on with my life?
1w
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
[quote='881081022, wu_aaron, /thread/818708?answerId=881081022#881081022, /profile/wu_aaron'] We have successfully connected an iOS device with a non-iOS device via Wi-Fi Aware [/quote] Nice! I know lots of folks have struggled to get that working, so I’m glad to hear of a success story. [quote='881081022, wu_aaron, /thread/818708?answerId=881081022#881081022, /profile/wu_aaron'] we still have a throughput issue … sends an HTTP request over an already-established TCP connection [/quote] So, just to be clear, are you using URLSession for this? Or have you implemented your own HTTP protocol on top of Network framework? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1w
Triggering “realtime” mode for peer-to-peer WiFi via awdl to fix jitter problems
This is a bit complicated to explain so bare with me. I am working on building an app that allows you to send real time video/camera captures from one Apple device to another. I am using a custom UDP protocol built on top of NWListener, NWBrowser, and NWConnection APIs. It works fine, but there are a few issues that seems to all be related to awdl: When transmitting via WiFi over the router (not using peer-to-peer), there are periodic interruptions when the wireless card on the device changes channels for awdl polling. This is resolved by changing the 5GHz WiFi channel on the router to channel 149 (or disabling AWDL altogether which is not really feasible). In order to work around number 1, I decided to build in an option to toggle/prefer peer-to-peer transmission in the app thinking that if everything goes over a peer-to-peer connection the jitter caused from the channel switching should go away. This also works, but with an important caveat. The default transmission is extremely choppy until you ta
3
0
133
1w
Reply to Triggering “realtime” mode for peer-to-peer WiFi via awdl to fix jitter problems
[quote='881114022, craigc123, /thread/819926?answerId=881114022#881114022, /profile/craigc123'] do you have any recommendations of things that might work here? [/quote] No, sorry. I try to avoid speculating in general, and especially so in cases like this. [quote='881114022, craigc123, /thread/819926?answerId=881114022#881114022, /profile/craigc123'] tried using the Multipeer Connectivity API [/quote] Multipeer Connectivity won’t help. It uses the same peer-to-peer Wi-Fi infrastructure as Network framework. Oh, and it’s best avoided anyway [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] One day I’ll succeed in my efforts to get that API officially deprecated, and I’ll sing a happy song while I update the advice in TN3151 and Moving from Multipeer Connectivity to Network Framework (-:
1w
Reply to App disappeared from App Store Connect - support unresponsive - Case 102841743378
Has anyone experienced an app disappearing from App Store Connect? Any advice on escalation would be appreciated. There have been a couple of cases where the app was automatically removed from the store after a software update even though the status said it was ready for distribution. It happened in March 5th. I've asked Apple, Inc. But there has been no explanation.
1w
Reply to MFMailComposeViewController in visionOS does not have a cancel button
[quote='881073022, chkpnt, /thread/748447?answerId=881073022#881073022, /profile/chkpnt'] Is this a bug or intentional? [/quote] I’d call it a bug, by my opinion doesn’t matter (-: If this is causing your product significant grief then it’s worth filing a bug about, even if it’s intentional. [quote='881095022, chkpnt, /thread/748447?answerId=881095022#881095022, /profile/chkpnt'] I've filed FB22313288. [/quote] Thanks. It’s been marked as a duplicate of a bug that was filed internally, one that’s definitely with the right folks. I don’t have any info to share beyond that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: General Tags:
1w
Reply to Securing XPC Daemon Communication from Authorization Plugin
I’m still not entirely sure what stage you’re at here. You started this thread talking about manually checking requirements, which is not what I recommend when dealing with XPC. Rather, you should apply the requirement directly to the XPC connection, as explained in this forums post. With that in mind, it’s a question of crafting the right requirement. There are two parts to this: Identifying your clients Identifying your code loaded into system clients Identifying your clients should be straightforward. You start with the DR of those clients and then adjust the Boolean logic to suit your specific needs. It’s not possible to identify your code loaded into system clients, so the best you can do is identify those systems clients themselves. And there’s no good way to do that: You could use the client’s designated requirement (DR), but that might break if the system changes the context in which it loads your authorisation plug-ins (as has happened in the past). You could use a much broader requirement, like anch
1w
Reply to App rejected under Guideline 2.1(a) - App Completeness. Seeking advice!
If your app has been rejected and you need help resolving the issue, consider taking advantage of one of the following support options available from App Review: Reply to the message from App Review in App Store Connect and request clarification. Request a call with an Apple representative to discuss the outcome of the review. Submit an appeal to the App Review Board if you believe your app follows the App Review Guidelines. Visit the Contact Us page on Apple Developer and select the App Review tile to learn more.
Replies
Boosts
Views
Activity
1w
No contact from Support and No Review (5 Months Now)
My investors are losing their minds. We’ve had our app available on Google since late December, but our experience with Apple has been a nightmare. First, despite paying the developer fee, nobody responds to emails or reaches out. The one time we got Apple on the phone, we spoke to someone who said she was in charge of the testing team reviewing our app. The call was frustrating—she didn’t seem familiar with basic app testing for a location-based product (for example, how to emulate a different location), and it left us feeling helpless. The technical ability of the testing process has been shocking. We spent a month just trying to get reviewers to understand the basic app concepts. Our app also isn’t available in the United States, which seemed to confuse the review team. We’ve been able to address feedback quickly—sometimes within an hour—yet here we are nearly five months later still stuck. Right now we are averaging about a week at best to two weeks. Our app works; we know this because i
Replies
7
Boosts
0
Views
321
Activity
1w
App Stuck in “In Review'' status
Hi everyone, My app has been stuck in In Review status for over 20 days with no updates. I submitted the app on March 1, 2026, the status changed to In Review on March 4, 2026, and after that no changes. App ID: 6755649144 I also reached out to Apple Developer Support on March 15 but haven't received any response. Support Case ID: 102845096494 Could someone from App Review please take a look? Also any advice on how to move things forward would be appreciated. Thank you!
Replies
1
Boosts
0
Views
62
Activity
1w
TestFlight In-App Purchase (Consumable) gets stuck when using real Apple ID – cannot repurchase even after finishTransaction
**Environment Platform:** iOS Distribution: TestFlight Product type: Consumable In-App Purchase Account used for testing: Real Apple ID (not Sandbox) StoreKit: StoreKit 1 iOS version: iOS 17+ (also reproduced on earlier versions) Issue Description We are encountering an issue when testing consumable in-app purchases in a TestFlight build using a real Apple ID. Under normal circumstances, consumable products should be purchasable repeatedly. However, in TestFlight, after a successful purchase flow, the same product may become unavailable for repurchase, and the transaction appears to be stuck, even though: • finishTransaction: is correctly called • The transaction state is .purchased • No pending transactions are left in the payment queue Once this happens, subsequent purchase attempts result in behavior similar to a non-consumable product (e.g. “already purchased” or no purchase UI shown).
Replies
4
Boosts
0
Views
246
Activity
1w
Reply to Rejected a couple of time for 5.1.1/5.1.2 - AI consent screen not seen by reviewers despite being first screen on launch
Thank you for the feedback. Let me clarify: My app is a SwiftUI iOS fitness app called GymFusion. It uses Anthropic's Claude AI API to power features like meal photo scanning, body composition analysis, and workout coaching. The rejection is solely about Guidelines 5.1.1(i) and 5.1.2(i) — the app shares user data with a third-party AI service (Anthropic) and Apple says the app doesn't clearly disclose this or ask for permission. There are no in-app purchase issues — apologies for any confusion. Here's what I've implemented: The app's entry point (RootView) shows the AI consent screen as the first view on every launch. It's not a sheet or popup — it's embedded in the view hierarchy: if auth.isLoading { // Loading screen } else if !consentManager.hasConsented && !consentManager.hasSeenConsent { AIConsentView() // Consent blocks the entire app } else if auth.isAuthenticated { MainTabView() } else { AuthView() } The consent screen: Lists all data shared (photos, workout history, body measurements
Replies
Boosts
Views
Activity
1w
Reply to Universal Links and Cloud-testing platforms
Hi, Thank you again for your continued guidance on this. Since Universal Links are part of our sign-in/login/authorization workflow, they are required for all of our testing workflows. Our cloud testing platform has indicated that if we distribute the app to them via the Apple Developer Enterprise Program, they would not need to re-sign it, which would preserve the Associated Domains entitlement and allow the sign-in flow to work correctly on their device farm. Since our app also needs to be published to the App Store, we would continue using our standard Apple Developer Program for that purpose. Is this a valid scenario? We want to stay within Apple's supported provisioning model. If maintaining both an Enterprise Program and a Developer Program membership is the right path forward, we are prepared to do that.
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
1w
Reply to FSKit passthrough sample fails to mount
[quote='881252022, alexfs123, /thread/819160?answerId=881252022#881252022, /profile/alexfs123'] I got a couple of kernel panics while developing a new plugin. [/quote] Kernel panics are always bugworthy. See Bug Reporting: How and Why? for my advice on how to file effective bug reports. And please post your bug number, just for the record. Honestly, I’d be surprised if these kernel panics were caused by FSKit. My experience is that kernel panics are usually caused by other subsystems within the kernel. However, the only way to know for sure is to get a bug on file. As to the behaviour of PassthroughFileSystem, keep in mind that it’s sample code, not a production file system. If you encounter weird problems, it’s worth investigating whether those issues are caused by FSKit or by the sample. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
1w
Reply to App Review Inefficiency
I'm in the middle of the same nightmare. Multiple rejections with no helpful information - very vague. No specifics that would allow me to make the required changes and resubmit. Filed an appeal, which was rejected. Set up a call, was told 3-5 business days, then on business day 4 was told another 3-5 business days. So disappointed in Apple. Can anyone tell me exactly what I need to do to pass review so I can do it and get on with my life?
Replies
Boosts
Views
Activity
1w
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
[quote='881081022, wu_aaron, /thread/818708?answerId=881081022#881081022, /profile/wu_aaron'] We have successfully connected an iOS device with a non-iOS device via Wi-Fi Aware [/quote] Nice! I know lots of folks have struggled to get that working, so I’m glad to hear of a success story. [quote='881081022, wu_aaron, /thread/818708?answerId=881081022#881081022, /profile/wu_aaron'] we still have a throughput issue … sends an HTTP request over an already-established TCP connection [/quote] So, just to be clear, are you using URLSession for this? Or have you implemented your own HTTP protocol on top of Network framework? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
1w
Triggering “realtime” mode for peer-to-peer WiFi via awdl to fix jitter problems
This is a bit complicated to explain so bare with me. I am working on building an app that allows you to send real time video/camera captures from one Apple device to another. I am using a custom UDP protocol built on top of NWListener, NWBrowser, and NWConnection APIs. It works fine, but there are a few issues that seems to all be related to awdl: When transmitting via WiFi over the router (not using peer-to-peer), there are periodic interruptions when the wireless card on the device changes channels for awdl polling. This is resolved by changing the 5GHz WiFi channel on the router to channel 149 (or disabling AWDL altogether which is not really feasible). In order to work around number 1, I decided to build in an option to toggle/prefer peer-to-peer transmission in the app thinking that if everything goes over a peer-to-peer connection the jitter caused from the channel switching should go away. This also works, but with an important caveat. The default transmission is extremely choppy until you ta
Replies
3
Boosts
0
Views
133
Activity
1w
Reply to Triggering “realtime” mode for peer-to-peer WiFi via awdl to fix jitter problems
[quote='881114022, craigc123, /thread/819926?answerId=881114022#881114022, /profile/craigc123'] do you have any recommendations of things that might work here? [/quote] No, sorry. I try to avoid speculating in general, and especially so in cases like this. [quote='881114022, craigc123, /thread/819926?answerId=881114022#881114022, /profile/craigc123'] tried using the Multipeer Connectivity API [/quote] Multipeer Connectivity won’t help. It uses the same peer-to-peer Wi-Fi infrastructure as Network framework. Oh, and it’s best avoided anyway [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] One day I’ll succeed in my efforts to get that API officially deprecated, and I’ll sing a happy song while I update the advice in TN3151 and Moving from Multipeer Connectivity to Network Framework (-:
Replies
Boosts
Views
Activity
1w
Reply to App disappeared from App Store Connect - support unresponsive - Case 102841743378
Has anyone experienced an app disappearing from App Store Connect? Any advice on escalation would be appreciated. There have been a couple of cases where the app was automatically removed from the store after a software update even though the status said it was ready for distribution. It happened in March 5th. I've asked Apple, Inc. But there has been no explanation.
Replies
Boosts
Views
Activity
1w
Reply to MFMailComposeViewController in visionOS does not have a cancel button
[quote='881073022, chkpnt, /thread/748447?answerId=881073022#881073022, /profile/chkpnt'] Is this a bug or intentional? [/quote] I’d call it a bug, by my opinion doesn’t matter (-: If this is causing your product significant grief then it’s worth filing a bug about, even if it’s intentional. [quote='881095022, chkpnt, /thread/748447?answerId=881095022#881095022, /profile/chkpnt'] I've filed FB22313288. [/quote] Thanks. It’s been marked as a duplicate of a bug that was filed internally, one that’s definitely with the right folks. I don’t have any info to share beyond that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to Securing XPC Daemon Communication from Authorization Plugin
I’m still not entirely sure what stage you’re at here. You started this thread talking about manually checking requirements, which is not what I recommend when dealing with XPC. Rather, you should apply the requirement directly to the XPC connection, as explained in this forums post. With that in mind, it’s a question of crafting the right requirement. There are two parts to this: Identifying your clients Identifying your code loaded into system clients Identifying your clients should be straightforward. You start with the DR of those clients and then adjust the Boolean logic to suit your specific needs. It’s not possible to identify your code loaded into system clients, so the best you can do is identify those systems clients themselves. And there’s no good way to do that: You could use the client’s designated requirement (DR), but that might break if the system changes the context in which it loads your authorisation plug-ins (as has happened in the past). You could use a much broader requirement, like anch
Replies
Boosts
Views
Activity
1w
Reply to 26.4 beta and RC versions are unable to be created on anything but 26.4 beta host OS
On my macOS 15.7.4 machine: $ pkgutil --pkg-info-plist com.apple.pkg.MobileDevice groups com.apple.findsystemfiles install-location Library/Apple/ install-time 1771452321 pkg-version 4.0.0.0.1.1762585687 pkgid com.apple.pkg.MobileDevice receipt-plist-version 1 volume /
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
1w