Delve into the world of built-in app and system services available to developers. Discuss leveraging these services to enhance your app's functionality and user experience.

Posts under General subtopic

Post

Replies

Boosts

Views

Activity

watchOS — Continuous Core Motion monitoring in the background for independent fall detection
I'm developing an independent fall-detection application for Apple Watch using Core Motion (CMMotionManager) at 20 Hz. The goal is to identify potential falls using accelerometer, gyroscope and orientation data, then notify nominated family contacts. The application is deliberately independent of Apple's built-in Fall Detection and Emergency SOS. Test environment Physical Apple Watch running watchOS 27.2 Xcode 27.2 Core Motion device-motion callbacks on a dedicated serial OperationQueue Motion processing on the MainActor Tests performed without the Xcode debugger attached Observed results With the Watch display awake: 2,300 processed samples Longest sensor timestamp gap: 0.05 seconds Longest callback arrival gap: 0.66 seconds Callback interruptions over one second: 0 With the Watch dimmed/backgrounded: 3,229 processed samples Longest sensor timestamp gap: 0.30 seconds Longest callback arrival gap: 29.11 seconds Callback interruptions over one second: 6 Maximum sample delivery lag: 29.065 seconds The motion timestamps appear nearly continuous, but callback delivery becomes substantially delayed after the app enters the background. The monitoring flag remains true, and no explicit call to stop motion updates occurs when the app becomes inactive. Questions Is there an Apple-supported background execution mechanism or entitlement allowing a third-party watchOS app to continuously process accelerometer and gyroscope data for independent fall detection, without requiring an active workout session? Would CMBatchedSensorManager provide any useful background delivery capability for this application, or would its callbacks remain subject to normal watchOS suspension? Is there a recommended architecture for detecting a potential fall and initiating a timely family notification while the Watch app is backgrounded, without relying on Apple's built-in Fall Detection or Emergency SOS? We understand that workout sessions and extended runtime sessions have specific intended purposes. We want to implement this correctly rather than use an unrelated background mode to prevent suspension. Any guidance from Apple engineers or developers experienced with watchOS background Core Motion processing would be greatly appreciated.
1
0
78
2h
Trying to create an developer account for a non-profit
We are a small non-profit that is trying to add Apple Pay as an option for donations to our website. I have done everything I need to do to create a developer account. An email was sent to the COO to verify that I have permission to set up the account. She missed the email and now the link is expired. I cannot find any way to resend the email link. We have been stuck in pending for over 2 months. I tried calling Apple support and googled everything I could possible think of. Is there a way to fix this?
0
0
19
2h
Full Disk Access on macOS 27.3
I'm looking into the changes being implemented and I find this way of handling by Apple on short notice problematic. Now our customers (those that don't have MDM) will have to jump through hoops to enable FDA for our product, a security product that also uses Endpoint Security. We already have the entitlement for endpoint security, which requires FDA in order to work, so why make it so difficult instead of just allowing FDA for apps that have this entitlement? Why only backup applications are exempted?
1
0
37
2h
Apple Developer Access
Good morning, For context, I am an Application Specialist at a K-12 school district. After initially enrolling for Apple Developer(AD), I receive an email every week from the AD team stating "We still need the documentation we requested [x] weeks ago in an email titled “Request for Enrollment Documents”. This email does not exist. Yes, I've checked my spam/junk folder, and I can provide screenshots from Outlook with all emails from AD if need be. I have been attempting to gain access for some time now, and have resorted to posting here as support is not responding to any emails or cases on the website. Here are some things I've tried in the last month or so: After being sent weekly emails to upload the unnamed “additional documentation”, discovered that my Apple account didn’t even have permissions to upload any files or create support tickets for Apple Developer specifically. Replied to at least five of these weekly emails asking for clarification. No response. Contacted our Apple rep, who did assist me assigning the proper permissions for my Apple account to access the AD website and submit tickets, but that’s the extent of what he could help me with. Called AD support directly, which has a robot answer and says something along the lines of “our support options have changed, please go to [URL for AD website]” before hanging up automatically. Used the link from one of the weekly emails to upload a picture of our enrollment ID, as well as entering the issues I’ve been having with this. No response. Submitted two AD tickets straight from their website, one being over a week old now. Still no response. I have the enrollment ID of course, but I don't believe that's something to be posted onto a public forum. Has anyone had similar issues with this? Do they just need our DUNS number? If so, why won't they actually tell me in their request for "additional documentation"? If anyone could assist me here, it would be greatly appreciated.
0
0
45
6h
Repeated App Store Rejections Under Guideline 4.3(a) Despite Following Apple's Instructions – Seeking Advice
ello everyone, I'm looking for advice from developers who have experienced repeated App Store rejections under Guideline 4.3(a), particularly in situations involving a previously published version of the same organization's application under another developer account. I'm developing and publishing an officially authorized application for Arise and Shine Heavenly Embassy. Unfortunately, I've been caught in a prolonged App Review process, and I'm struggling to find a clear path toward resolving the issue. Background There was a previous Arise & Shine application published under a former developer's Apple Developer account. I subsequently developed a new version of the application under my own Apple Developer account, with authorization from the organization. During the review process, Apple repeatedly rejected the new application under Guideline 4.3(a) – Spam. I understand Apple's concerns about duplicate applications and appreciate the need to maintain quality on the App Store. However, I have been trying to resolve this matter in good faith. What I've done so far Communicated with Apple App Review regarding the rejection. Attended a discussion with an Apple representative to understand the concerns. Followed the instructions to investigate and remove the previous application. Accessed the former developer's account and attempted to remove the previous application. Discovered that the removal could not be completed because the former developer's Apple Developer Program membership had expired. Explained this limitation to Apple and provided supporting evidence. Was subsequently encouraged to resubmit the application, which I did in good faith. Unfortunately, the application was rejected again under the same guideline. What makes this particularly difficult is that I still haven't received a sufficiently specific explanation of what exactly is triggering Guideline 4.3(a), or what concrete changes Apple expects me to make. Where I need help I would appreciate insights from developers who have experienced similar situations. Specifically: Can an application be rejected under Guideline 4.3(a) because a previous version of the same organization's app remains on the App Store under another developer account? If the previous developer's membership has expired and the application cannot be removed through that account, what is the appropriate process for resolving this? Is there an established procedure for transferring an application or resolving duplicate-app concerns when the original developer account is no longer active? How can a developer get a case escalated to an App Review specialist who can examine the complete history of previous discussions and submissions? I have also requested another phone call with App Review because I believe a direct discussion would be more productive than continuing through repeated rejections without specific guidance. What I'm hoping to achieve I am not asking Apple to overlook its guidelines or grant special treatment. I simply want to understand the precise issue, follow the appropriate procedure, and get this officially authorized application reviewed on its actual merits. I've invested considerable time and resources into this project, and it is frustrating to remain stuck despite making genuine efforts to cooperate. If anyone from the developer community has navigated a similar situation, I would genuinely appreciate hearing how you resolved it. Thank you.
0
0
12
7h
iOS 27: domain-bound SMS one-time codes are not offered in an associated app ("Could not fetch application record"), worked on iOS 26.6 and 18
Since iOS 27.0, domain-bound SMS one-time codes are no longer offered above the keyboard in our app, where the code is entered on a web page in a WKWebView, although the app is associated with the domain through webcredentials. The same SMS is offered in Safari on the same device, and it is offered in our app on iOS 26.6 and iOS 18. SMS format (last line per the domain-bound code format): Your verification code is: 123456 @app.example.com #123456Setup Several builds of the same app with different bundle IDs (App Store, internal, development), all under one team Entitlement com.apple.developer.associated-domains: webcredentials:app.example.com (plus two more environments of the same domain) AASA at https://app.example.com/.well-known/apple-app-site-association: 200, application/json, no redirect, same content on app-site-association.cdn-apple.com: {"webcredentials":{"apps":["TEAMID.com.example.app","TEAMID.com.example.app.internal","TEAMID.com.example.app.dev"]}} The code field is an <input type="tel" autocomplete="one-time-code"> in a WKWebView showing a page on that domain. We also tested a native field with the one-time-code content type (the app is built with Flutter; the field is a Flutter TextField with the one-time-code autofill hint). Steps Open the verification page in the app and focus the code field. Receive the SMS above. Expected: the code is offered in the QuickType bar, as it is in Safari on the same domain and as it is in our app on iOS 26.6 and iOS 18. Actual: nothing is offered. The keyboard log: kbd Received verification code from Messages kbd One Time Code field has been entered. kbd Retrieving Current One-Time Codes for App kbd Current verification code is domain-bound to <mask.hash: '…'>. kbd Domain-bound verification code is NOT valid for app <mask.hash: 'X'>. E kbd Could not fetch application record for application identifier: <mask.hash: 'X'>. kbd Returning 0 available one-time codesWhat we checked swcd downloads the AASA for all domains without errors after a reinstall. The installed app's entitlements (read from the device) contain the expected application-identifier and associated domains; the profile is validated. The failure is the same in the WKWebView field and in a native one-time-code field, in the App Store build, a distribution-signed internal build and a development build, and in an older app version that used to work. The masked application identifier in the log (X above) is the same for two builds with different bundle IDs, so the lookup does not seem to use the app's bundle ID. All our builds share CFBundleExecutable = Runner (the Flutter default) and the same CFBundleName. The same app build and the same SMS work on iOS 26.6 and iOS 18.x, so the change happened between iOS 26.6 and 27.0. An SMS without the @domain #code line is offered in the app on iOS 27 (Returning 1 available one-time code), although Could not fetch application record is still logged. Questions Is this a known iOS 27 regression, or is there a new requirement for apps to receive domain-bound codes? What application identifier does the keyboard use for this lookup, and can anything in the app's configuration (for example the executable name) affect it? Device: iPhone 17 Pro Max, iOS 27.0
8
3
993
1d
Screen Time reaches the iPhone Instagram limit after Mac sync while Instagram is in the background (on both devices)
Hello, I have noticed, once again, that DeviceActivityMonitors are quite frustrating to work with, since they are triggering random events when using mulitple Apple devices. For example, if Instagram is open on some random (non-foreground!) tab in Safari on the Mac, the iPhone will reach its limit quite consistently & quickly atfer setting up a new device activity threshold. It would be great if A) background usage was not counted towards screen time: FB25576930 B) there was an API for us developers to set-up device-specific deviceactivitymonitors: FB24363336 Hope that helps!
0
0
98
3d
URGENT: Muse is AUTOMATICALLY blocked by Screen Time API whenever Facebook is blocked, 100% of the time with no workaround for users or developers
PLEASE ADDRESS ASAP: Muse is #1 on the App Store and Facebook is one of the most blocked apps for Screen Time. This is affecting a vast number of people. Description: When a user blocks the Facebook app in any screen time app, iOS automatically blocks Meta's Muse app too. Every single time. There is no way for the user or the developer to prevent it, allowlist it, or even detect that it happened. Muse shows Apple's generic blocked-app "Restricted" screen instead of the screen time app's own design, so the user cannot tell who blocked it or why. This is the worst possible combination of apps: Facebook is one of the most-blocked app across screen time apps. Muse ("Muse from Meta") is currently the #1 app on the App Store. A huge and fast-growing number of users block Facebook and silently lose the world's most popular new app. Muse launched Sept 8, 2026 and adoption is still climbing -- the affected population grows every day. There is NO workaround whatsoever: Users cannot allowlist Muse: it does not appear in Settings > Screen Time > Always Allowed. Developers cannot prevent it: the Screen Time API offers no opt-out; the extra block is applied by iOS itself. Developers cannot detect it: Muse's token (listed separately in FamilyActivityPicker) corresponds to no real identity anywhere else. Developers cannot customize it: their ShieldConfiguration is never consulted -- Muse gets Apple's generic shield UI. Users cannot even block Muse on purpose: shielding Muse's own token is a silent no-op. Screen Time usage statistics are also wrong -- Muse usage is recorded as "Facebook." This Screen Time bug renders screen time apps effectively unusable if users want to block Facebook and use Muse, which is extremely common. How can we get this addressed as soon as possible? Feedback Assistant ticket: https://feedbackassistant.apple.com/feedback/25019832
9
9
686
3d
Autoupdate of macOS app via Sparkle library fails
We have a macOS app distributed outside of the Mac App Store (Developer ID distribution). It incorporates the popular Sparkle library which offers autoupdate functionality (downloading and installing new versions of the app). The autoupdate functionality worked flawlessly for many years but with recent versions of macOS it started failing. To demonstrate the problem we offer the dts-demo.tar.gz file (available for download, see the links below). That file contains the sources of DemoApp and a build_packages.sh script that builds installer packages for two versions of DemoApp. The old version is 3.0 and the new version is 4.0. Manually installing the old version (by double-clicking the .pkg file and following the instructions) succeeds. After launching the app, trying to autoupdate to the new version by clicking the "Check for update" button fails. The process starts, the old version is deinstalled but then the installation of the new version fails. Manually installing the new version of the app over the old version succeeds. The problem has been observed on macOS versions after 26.6.2 (e.g. 26.7.3 or 27.0). The files we offer for download are: dts-demo.tar.gz at https://dx4vjdxzj60n5.cloudfront.net/dts-demo.tar.gz manual_install_v3.log at https://dx4vjdxzj60n5.cloudfront.net/manual_install_v3.log autoupdate_to_v4.log at https://dx4vjdxzj60n5.cloudfront.net/autoupdate_to_v4.log manual_install_v4_over_v3.log at https://dx4vjdxzj60n5.cloudfront.net/manual_install_v4_over_v3.log The provided log files are excerpts from the system's install.log file. The Sparkle framework included in dts-demo.tar.gz comes from the official Sparkle 2.10.1 release. That version is the latest available at the time of writing. Please note that it only accepts URLs with 'http' or 'https' schemes. This autoupdate problem looks like a bug in macOS because manual updates succeed. We'd like to have the bug fixed or at least find a workaround.
3
0
74
5d
CXCallUpdate not working for outgoing calls
I try to update remoteHandle using CXCallUpdate for outgoing call, but this works only on iOS 15 but not on 17 or 18 (16 didn't test). This problem actual only for outgoing calls, but for incoming calls update works fine. func startOutgoingCall(with callID: UUID, userID: String) { let handle = CXHandle(type: .generic, value: userID) let action = CXStartCallAction(call: callID, handle: handle) callController.requestTransaction(with: action) { [weak self] error in // ... } } func updateOutgoingCall(with callID: UUID, groupID: String) { let update = CXCallUpdate() update.remoteHandle = CXHandle(type: .generic, value: groupID) provider.reportCall(with: callID, updated: update) } I also tried phoneNumber type but it seems initial handle that I set to CXStartCallAction not possible to change (value or even type). I use this handle value to implement recall by tap on call in Recents tab of system address book. But since my calls can transform from p2p to group call, I need to update handle value or find some another way to pass call identification info.
5
1
1.4k
5d
Can an iOS app share Screen Time goal progress with friends?
I'm developing an app that helps users reduce social media usage through friendly competitions. With explicit permission, the app would track daily and weekly usage of selected apps like Instagram, TikTok, and YouTube. Users could voluntarily share their live total usage, percentage improvement, or goal-completion status with approved friends. Does Apple's Family Controls policy permit this? If not, is there an approved way to implement a friends leaderboard using Screen Time data? Thank you!
0
0
47
5d
Declared Age Range in sandbox: no sheet at launch, and the set per scenario
We are testing the Declared Age Range API with sandbox testers on an iPhone 17e with iOS 26.6.2 (Xcode 26.6, iOS 26.5 SDK). The app is not yet released; everything here is pre-release testing. We have filed three focused reports: FB25530441 (requestAgeRange returned .declinedSharing with no sheet), FB25530501 (the age that Age Assurance first shows at a sign-in against what the API reads), and FB25530513 (a selected scenario not reflected in requiredRegulatoryFeatures). Four questions remain that are not defects: When a sandbox tester has an Age Assurance scenario selected, should requestAgeRange present the sheet at launch, or answer from the scenario without showing one? Is there a way to see the sheet at launch in sandbox, as a first-time user would, so we can test the share and decline paths end to end? The article "Requesting people's age range information in your app" says the set's values "tell you which actions you need to take for compliance", and the sandbox page lists each scenario's age range, but we found neither saying which members each scenario produces. Please confirm: for each Age Assurance scenario, and for a tester with no scenario selected, what should requiredRegulatoryFeatures contain? Does the tester's App Store territory or creation date matter in sandbox? On 1 and 2. Our app calls requestAgeRange at launch when requiredRegulatoryFeatures contains .declaredAgeRangeRequired. On four days between October 31 and November 7, 2026, at every launch where we know it did make the request, Apple's age range sheet did not appear. Some requests we made by hand from a debug console returned the scenario's range with no sheet: on November 7, one on each of two testers on '13 - 15' returned a shared range of 13 to 15. One such request on October 31 did present the sheet; it is the only sheet on record across the four days (at a few launches the sheet was not written down separately). On 3. What we read on one tester, in this order, each scenario read before and after a relaunch unless noted: No scenario selected (signed in for the first time; Age Assurance showed no option selected), read after a relaunch only: none of the three members. '13 - 15, significant change approved', then '16 - 17, significant change declined', then 'Under 13, significant change approved': .declaredAgeRangeRequired and .significantAppChangeRequiresParentalConsent. '18+, age confirmed, significant change not applicable': .declaredAgeRangeRequired only. '18+, age confirmed, significant change applicable': .declaredAgeRangeRequired and .significantAppChangeRequiresAdultNotification. '18+, age not confirmed, significant change not applicable': .declaredAgeRangeRequired only. For these rows we read contains for the three members the iOS 26.5 SDK defines, so a member outside those three would not show. On November 5 we printed the whole set on 15 reads of sandbox testers, and no other member appeared.
0
0
69
1w
PDF Widget Annotations Disappear After Saving in PDFKit (including with Preview)
The Problem When a user toggles radio buttons or checkboxes in a PDF using Preview, the widgets disappear following subsequent interactions after the file is saved and reopened. This renders the form fields unusable. Steps to Reproduce the Problem Open a PDF with radio buttons or checkboxes in Preview. Toggle a radio button or checkbox. Save and close the file. Re-open the PDF in Preview. Toggle the same button again. The button (and any others with the same field name) will disappear. Expected Results Toggling a radio button or checkbox should update the field value without causing the button (or related buttons) to disappear. This behavior is consistent with previous versions of PDFKit. What is Happening In Preview, interacting with radio buttons and checkboxes correctly updates their appearance as expected. Saving the PDF, however, causes the appearance dictionary to reference a new N entry that is a single appearance stream unassociated with any state. The annotation's AS entry is not updated. The original N entry remains but is no longer referenced. Subsequent interactions fail to update the visual presentation because the appearance stream is missing. Impact on User Experience Radio buttons and checkboxes may disappear and become unusable when toggled. PDF documents become irreparably altered after a button is toggled and the file is saved. PDF file size significantly increases when the file is saved. Users may believe they have successfully completed a form, only for the data to become inaccessible or invisible to recipients. Forms may need to be completely restarted or recreated from scratch if the original becomes unusable. The corrupted PDF structure might cause the file to render incorrectly or crash in third-party PDF viewers. Affected Apps/OSs Tested with Preview 11.0 (1147), as well as other apps that use PDFKit, on macOS Golden Gate 27.0 (26A428). This problem also affects PDFKit on iOS 27.0 and iPadOS 27.0. Feedback/bug report: FB24866826 Related Sample Output Original PDF File Checkbox widget annotation (6 0 obj), its appearance dictionary (17 0 obj), and normal appearance dictionary (18 0 obj). Button is not checked. 6 0 obj << /Border [ 0 0 0 ] /Rect [ 90 390 110 410 ] /T (button1) /F 4 /Subtype /Widget /DA (/.AppleSystemUIFont 13 Tf 0 g) /MK 16 0 R /C [ 0 ] /AP 17 0 R /V /Off /M (D:20260919225320Z00'00') /AS /Off /FT /Btn /Type /Annot /Ff 0 >> endobj 17 0 obj << /N 18 0 R >> endobj 18 0 obj << /Yes 20 0 R /Off 22 0 R >> endobj PDF File after Save Checkbox widget annotation object (6 0 obj), its new appearance dictionary object (8 0 obj), a new normal appearance stream object (20 0 obj), and the original appearance stream dictionary (now 21 0 obj). File saved after user checked button. 6 0 obj << /Ff 0 /Type /Annot /AS /Off /AP 8 0 R /MK 9 0 R /C [ 0 ] /FT /Btn /M (D:20260919225320Z00'00') /DA (/.AppleSystemUIFont 13 Tf 0 g) /Subtype /Widget /F 4 /Border [ 0 0 0 ] /Rect [ 90 390 110 410 ] /T (button1) /V (Yes) >> endobj 8 0 obj << /N 20 0 R >> endobj 20 0 obj << /Filter /FlateDecode /Resources << /ColorSpace << /CS1 [ /ICCBased 29 0 R ] /CS2 [ /ICCBased 30 0 R ] >> >> /BBox [ 0 0 20 20 ] /Type /XObject /Subtype /Form /Length 123 >> stream x UéA ¬0 Ô}≈|†≈nà¢úÛÇ* —SA =}Ïr(»ñµ≤w◊€YËà’|ÙÎŒç'óRï∂#SäÏÌü∞¢S‰Ì§ôRÌX }–É•åY Éçˆ BŒ H " *â´8™ˆZø6z⁄ÿ ”ú6ɀ੠"∫t˘‹;'¬ endstream endobj 21 0 obj << /Off 22 0 R /Yes 23 0 R >> endobj Note: No object references 21 0 obj in the PDF.
5
0
1.1k
1w
PDF Widget Annotations appear Pixelated/Rasterized
The Problem On opening a PDF document in the Preview app, PDF widget annotations appear pixelated/rasterized. This problem exists with button, text, and choice widget subtypes. The pixelation becomes more apparent when zoomed in. Expected Results PDF widgets should appear sharp and smooth, without pixelation. In previous versions of the Preview app, widgets appear vector-based as expected. Impact on User Experience PDF widgets appear pixelated and inconsistent with text content in the same PDF document. Widgets do not look like elements of an interactive form but, instead, resemble low-quality embedded images. Affected Apps/OSs: Preview 11.0 (1147), as well as other apps that use PDFKit, on macOS Golden Gate 27.0 (26A428). A similar problem appears to affect PDFKit on iOS 27.0 and iPadOS 27.0 as well. Feedback/bug report: FB24843022
8
3
1.7k
1w
Declared Age Range: fallback behavior, cached results, and older iOS versions
Hello, I am preparing an 18+ workout logging app for iOS and would like to clarify the supported behavior of the Declared Age Range framework before completing its integration. Workout records, body measurements and saved videos are stored locally. Outside additional regulatory requirements, the planned entry flow uses a neutral adult self-declaration without collecting a date of birth or identity documents. The intended storefronts are Japan, the United States, the United Kingdom, Canada, Australia, New Zealand, Ireland and Singapore. These are implementation-design questions, not errors reproduced in a completed DAR integration. I am seeking documented API/platform behavior, not legal approval. Applicability checks that fail If isEligibleForAgeFeatures throws, returns notAvailable, or does not complete, is there a supported fallback signal or recommended retry strategy? I would not interpret an error as a successful “outside regulated scope” result. Is there a documented platform requirement for app access while applicability remains unresolved, separate from developers’ obligations under applicable law? Previously returned adult age ranges If declaredAgeRangeRequired applies and requestAgeRange fails after an earlier adult response, does Apple support relying on an app-stored result? I understand that the system caches responses; my question concerns a result stored separately by the app. Is there a supported way to detect when that result must be invalidated because of an Apple Account change, changes to age information, or sharing/consent changes? If no such signal exists, what implementation pattern does Apple recommend? I would not assume that a previous result always belongs to the current person or invent a cache lifetime. Earlier OS versions For affected newly created Apple Accounts in regulated regions, what supported path applies on: iOS versions without Declared Age Range; iOS 26.0–26.1, without isEligibleForAgeFeatures; iOS 26.2–26.3, without requiredRegulatoryFeatures? The age-assurance Q&A discusses existing Apple Accounts on iOS 18 or earlier. Is there additional documentation covering newly created affected accounts on earlier OS versions? While checks remain unresolved, the proposed design withholds advertising and new purchases and preserves existing data with free export. This is a proposed design, not an assumption that local recording is exempt from any requirement. References reviewed: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app Pointers to relevant documentation or sample code would be appreciated. Thank you.
0
0
41
1w
watchOS — Continuous Core Motion monitoring in the background for independent fall detection
I'm developing an independent fall-detection application for Apple Watch using Core Motion (CMMotionManager) at 20 Hz. The goal is to identify potential falls using accelerometer, gyroscope and orientation data, then notify nominated family contacts. The application is deliberately independent of Apple's built-in Fall Detection and Emergency SOS. Test environment Physical Apple Watch running watchOS 27.2 Xcode 27.2 Core Motion device-motion callbacks on a dedicated serial OperationQueue Motion processing on the MainActor Tests performed without the Xcode debugger attached Observed results With the Watch display awake: 2,300 processed samples Longest sensor timestamp gap: 0.05 seconds Longest callback arrival gap: 0.66 seconds Callback interruptions over one second: 0 With the Watch dimmed/backgrounded: 3,229 processed samples Longest sensor timestamp gap: 0.30 seconds Longest callback arrival gap: 29.11 seconds Callback interruptions over one second: 6 Maximum sample delivery lag: 29.065 seconds The motion timestamps appear nearly continuous, but callback delivery becomes substantially delayed after the app enters the background. The monitoring flag remains true, and no explicit call to stop motion updates occurs when the app becomes inactive. Questions Is there an Apple-supported background execution mechanism or entitlement allowing a third-party watchOS app to continuously process accelerometer and gyroscope data for independent fall detection, without requiring an active workout session? Would CMBatchedSensorManager provide any useful background delivery capability for this application, or would its callbacks remain subject to normal watchOS suspension? Is there a recommended architecture for detecting a potential fall and initiating a timely family notification while the Watch app is backgrounded, without relying on Apple's built-in Fall Detection or Emergency SOS? We understand that workout sessions and extended runtime sessions have specific intended purposes. We want to implement this correctly rather than use an unrelated background mode to prevent suspension. Any guidance from Apple engineers or developers experienced with watchOS background Core Motion processing would be greatly appreciated.
Replies
1
Boosts
0
Views
78
Activity
2h
Trying to create an developer account for a non-profit
We are a small non-profit that is trying to add Apple Pay as an option for donations to our website. I have done everything I need to do to create a developer account. An email was sent to the COO to verify that I have permission to set up the account. She missed the email and now the link is expired. I cannot find any way to resend the email link. We have been stuck in pending for over 2 months. I tried calling Apple support and googled everything I could possible think of. Is there a way to fix this?
Replies
0
Boosts
0
Views
19
Activity
2h
Full Disk Access on macOS 27.3
I'm looking into the changes being implemented and I find this way of handling by Apple on short notice problematic. Now our customers (those that don't have MDM) will have to jump through hoops to enable FDA for our product, a security product that also uses Endpoint Security. We already have the entitlement for endpoint security, which requires FDA in order to work, so why make it so difficult instead of just allowing FDA for apps that have this entitlement? Why only backup applications are exempted?
Replies
1
Boosts
0
Views
37
Activity
2h
Apple Developer Access
Good morning, For context, I am an Application Specialist at a K-12 school district. After initially enrolling for Apple Developer(AD), I receive an email every week from the AD team stating "We still need the documentation we requested [x] weeks ago in an email titled “Request for Enrollment Documents”. This email does not exist. Yes, I've checked my spam/junk folder, and I can provide screenshots from Outlook with all emails from AD if need be. I have been attempting to gain access for some time now, and have resorted to posting here as support is not responding to any emails or cases on the website. Here are some things I've tried in the last month or so: After being sent weekly emails to upload the unnamed “additional documentation”, discovered that my Apple account didn’t even have permissions to upload any files or create support tickets for Apple Developer specifically. Replied to at least five of these weekly emails asking for clarification. No response. Contacted our Apple rep, who did assist me assigning the proper permissions for my Apple account to access the AD website and submit tickets, but that’s the extent of what he could help me with. Called AD support directly, which has a robot answer and says something along the lines of “our support options have changed, please go to [URL for AD website]” before hanging up automatically. Used the link from one of the weekly emails to upload a picture of our enrollment ID, as well as entering the issues I’ve been having with this. No response. Submitted two AD tickets straight from their website, one being over a week old now. Still no response. I have the enrollment ID of course, but I don't believe that's something to be posted onto a public forum. Has anyone had similar issues with this? Do they just need our DUNS number? If so, why won't they actually tell me in their request for "additional documentation"? If anyone could assist me here, it would be greatly appreciated.
Replies
0
Boosts
0
Views
45
Activity
6h
Repeated App Store Rejections Under Guideline 4.3(a) Despite Following Apple's Instructions – Seeking Advice
ello everyone, I'm looking for advice from developers who have experienced repeated App Store rejections under Guideline 4.3(a), particularly in situations involving a previously published version of the same organization's application under another developer account. I'm developing and publishing an officially authorized application for Arise and Shine Heavenly Embassy. Unfortunately, I've been caught in a prolonged App Review process, and I'm struggling to find a clear path toward resolving the issue. Background There was a previous Arise & Shine application published under a former developer's Apple Developer account. I subsequently developed a new version of the application under my own Apple Developer account, with authorization from the organization. During the review process, Apple repeatedly rejected the new application under Guideline 4.3(a) – Spam. I understand Apple's concerns about duplicate applications and appreciate the need to maintain quality on the App Store. However, I have been trying to resolve this matter in good faith. What I've done so far Communicated with Apple App Review regarding the rejection. Attended a discussion with an Apple representative to understand the concerns. Followed the instructions to investigate and remove the previous application. Accessed the former developer's account and attempted to remove the previous application. Discovered that the removal could not be completed because the former developer's Apple Developer Program membership had expired. Explained this limitation to Apple and provided supporting evidence. Was subsequently encouraged to resubmit the application, which I did in good faith. Unfortunately, the application was rejected again under the same guideline. What makes this particularly difficult is that I still haven't received a sufficiently specific explanation of what exactly is triggering Guideline 4.3(a), or what concrete changes Apple expects me to make. Where I need help I would appreciate insights from developers who have experienced similar situations. Specifically: Can an application be rejected under Guideline 4.3(a) because a previous version of the same organization's app remains on the App Store under another developer account? If the previous developer's membership has expired and the application cannot be removed through that account, what is the appropriate process for resolving this? Is there an established procedure for transferring an application or resolving duplicate-app concerns when the original developer account is no longer active? How can a developer get a case escalated to an App Review specialist who can examine the complete history of previous discussions and submissions? I have also requested another phone call with App Review because I believe a direct discussion would be more productive than continuing through repeated rejections without specific guidance. What I'm hoping to achieve I am not asking Apple to overlook its guidelines or grant special treatment. I simply want to understand the precise issue, follow the appropriate procedure, and get this officially authorized application reviewed on its actual merits. I've invested considerable time and resources into this project, and it is frustrating to remain stuck despite making genuine efforts to cooperate. If anyone from the developer community has navigated a similar situation, I would genuinely appreciate hearing how you resolved it. Thank you.
Replies
0
Boosts
0
Views
12
Activity
7h
iOS 27: domain-bound SMS one-time codes are not offered in an associated app ("Could not fetch application record"), worked on iOS 26.6 and 18
Since iOS 27.0, domain-bound SMS one-time codes are no longer offered above the keyboard in our app, where the code is entered on a web page in a WKWebView, although the app is associated with the domain through webcredentials. The same SMS is offered in Safari on the same device, and it is offered in our app on iOS 26.6 and iOS 18. SMS format (last line per the domain-bound code format): Your verification code is: 123456 @app.example.com #123456Setup Several builds of the same app with different bundle IDs (App Store, internal, development), all under one team Entitlement com.apple.developer.associated-domains: webcredentials:app.example.com (plus two more environments of the same domain) AASA at https://app.example.com/.well-known/apple-app-site-association: 200, application/json, no redirect, same content on app-site-association.cdn-apple.com: {"webcredentials":{"apps":["TEAMID.com.example.app","TEAMID.com.example.app.internal","TEAMID.com.example.app.dev"]}} The code field is an <input type="tel" autocomplete="one-time-code"> in a WKWebView showing a page on that domain. We also tested a native field with the one-time-code content type (the app is built with Flutter; the field is a Flutter TextField with the one-time-code autofill hint). Steps Open the verification page in the app and focus the code field. Receive the SMS above. Expected: the code is offered in the QuickType bar, as it is in Safari on the same domain and as it is in our app on iOS 26.6 and iOS 18. Actual: nothing is offered. The keyboard log: kbd Received verification code from Messages kbd One Time Code field has been entered. kbd Retrieving Current One-Time Codes for App kbd Current verification code is domain-bound to <mask.hash: '…'>. kbd Domain-bound verification code is NOT valid for app <mask.hash: 'X'>. E kbd Could not fetch application record for application identifier: <mask.hash: 'X'>. kbd Returning 0 available one-time codesWhat we checked swcd downloads the AASA for all domains without errors after a reinstall. The installed app's entitlements (read from the device) contain the expected application-identifier and associated domains; the profile is validated. The failure is the same in the WKWebView field and in a native one-time-code field, in the App Store build, a distribution-signed internal build and a development build, and in an older app version that used to work. The masked application identifier in the log (X above) is the same for two builds with different bundle IDs, so the lookup does not seem to use the app's bundle ID. All our builds share CFBundleExecutable = Runner (the Flutter default) and the same CFBundleName. The same app build and the same SMS work on iOS 26.6 and iOS 18.x, so the change happened between iOS 26.6 and 27.0. An SMS without the @domain #code line is offered in the app on iOS 27 (Returning 1 available one-time code), although Could not fetch application record is still logged. Questions Is this a known iOS 27 regression, or is there a new requirement for apps to receive domain-bound codes? What application identifier does the keyboard use for this lookup, and can anything in the app's configuration (for example the executable name) affect it? Device: iPhone 17 Pro Max, iOS 27.0
Replies
8
Boosts
3
Views
993
Activity
1d
CrashReporterExtension does not work on MacOS.
The new CrashReporterExtension is documented as working on MacOS, but the system extension definition disagrees, it only shows it as working on iOS: /System/Library/ExtensionKit/ExtensionPoints/com.apple.crash-reporter.extension.appexpt How can we work around that problem?
Replies
1
Boosts
0
Views
53
Activity
1d
Screen Time reaches the iPhone Instagram limit after Mac sync while Instagram is in the background (on both devices)
Hello, I have noticed, once again, that DeviceActivityMonitors are quite frustrating to work with, since they are triggering random events when using mulitple Apple devices. For example, if Instagram is open on some random (non-foreground!) tab in Safari on the Mac, the iPhone will reach its limit quite consistently & quickly atfer setting up a new device activity threshold. It would be great if A) background usage was not counted towards screen time: FB25576930 B) there was an API for us developers to set-up device-specific deviceactivitymonitors: FB24363336 Hope that helps!
Replies
0
Boosts
0
Views
98
Activity
3d
URGENT: Muse is AUTOMATICALLY blocked by Screen Time API whenever Facebook is blocked, 100% of the time with no workaround for users or developers
PLEASE ADDRESS ASAP: Muse is #1 on the App Store and Facebook is one of the most blocked apps for Screen Time. This is affecting a vast number of people. Description: When a user blocks the Facebook app in any screen time app, iOS automatically blocks Meta's Muse app too. Every single time. There is no way for the user or the developer to prevent it, allowlist it, or even detect that it happened. Muse shows Apple's generic blocked-app "Restricted" screen instead of the screen time app's own design, so the user cannot tell who blocked it or why. This is the worst possible combination of apps: Facebook is one of the most-blocked app across screen time apps. Muse ("Muse from Meta") is currently the #1 app on the App Store. A huge and fast-growing number of users block Facebook and silently lose the world's most popular new app. Muse launched Sept 8, 2026 and adoption is still climbing -- the affected population grows every day. There is NO workaround whatsoever: Users cannot allowlist Muse: it does not appear in Settings > Screen Time > Always Allowed. Developers cannot prevent it: the Screen Time API offers no opt-out; the extra block is applied by iOS itself. Developers cannot detect it: Muse's token (listed separately in FamilyActivityPicker) corresponds to no real identity anywhere else. Developers cannot customize it: their ShieldConfiguration is never consulted -- Muse gets Apple's generic shield UI. Users cannot even block Muse on purpose: shielding Muse's own token is a silent no-op. Screen Time usage statistics are also wrong -- Muse usage is recorded as "Facebook." This Screen Time bug renders screen time apps effectively unusable if users want to block Facebook and use Muse, which is extremely common. How can we get this addressed as soon as possible? Feedback Assistant ticket: https://feedbackassistant.apple.com/feedback/25019832
Replies
9
Boosts
9
Views
686
Activity
3d
Autoupdate of macOS app via Sparkle library fails
We have a macOS app distributed outside of the Mac App Store (Developer ID distribution). It incorporates the popular Sparkle library which offers autoupdate functionality (downloading and installing new versions of the app). The autoupdate functionality worked flawlessly for many years but with recent versions of macOS it started failing. To demonstrate the problem we offer the dts-demo.tar.gz file (available for download, see the links below). That file contains the sources of DemoApp and a build_packages.sh script that builds installer packages for two versions of DemoApp. The old version is 3.0 and the new version is 4.0. Manually installing the old version (by double-clicking the .pkg file and following the instructions) succeeds. After launching the app, trying to autoupdate to the new version by clicking the "Check for update" button fails. The process starts, the old version is deinstalled but then the installation of the new version fails. Manually installing the new version of the app over the old version succeeds. The problem has been observed on macOS versions after 26.6.2 (e.g. 26.7.3 or 27.0). The files we offer for download are: dts-demo.tar.gz at https://dx4vjdxzj60n5.cloudfront.net/dts-demo.tar.gz manual_install_v3.log at https://dx4vjdxzj60n5.cloudfront.net/manual_install_v3.log autoupdate_to_v4.log at https://dx4vjdxzj60n5.cloudfront.net/autoupdate_to_v4.log manual_install_v4_over_v3.log at https://dx4vjdxzj60n5.cloudfront.net/manual_install_v4_over_v3.log The provided log files are excerpts from the system's install.log file. The Sparkle framework included in dts-demo.tar.gz comes from the official Sparkle 2.10.1 release. That version is the latest available at the time of writing. Please note that it only accepts URLs with 'http' or 'https' schemes. This autoupdate problem looks like a bug in macOS because manual updates succeed. We'd like to have the bug fixed or at least find a workaround.
Replies
3
Boosts
0
Views
74
Activity
5d
CXCallUpdate not working for outgoing calls
I try to update remoteHandle using CXCallUpdate for outgoing call, but this works only on iOS 15 but not on 17 or 18 (16 didn't test). This problem actual only for outgoing calls, but for incoming calls update works fine. func startOutgoingCall(with callID: UUID, userID: String) { let handle = CXHandle(type: .generic, value: userID) let action = CXStartCallAction(call: callID, handle: handle) callController.requestTransaction(with: action) { [weak self] error in // ... } } func updateOutgoingCall(with callID: UUID, groupID: String) { let update = CXCallUpdate() update.remoteHandle = CXHandle(type: .generic, value: groupID) provider.reportCall(with: callID, updated: update) } I also tried phoneNumber type but it seems initial handle that I set to CXStartCallAction not possible to change (value or even type). I use this handle value to implement recall by tap on call in Recents tab of system address book. But since my calls can transform from p2p to group call, I need to update handle value or find some another way to pass call identification info.
Replies
5
Boosts
1
Views
1.4k
Activity
5d
Can an iOS app share Screen Time goal progress with friends?
I'm developing an app that helps users reduce social media usage through friendly competitions. With explicit permission, the app would track daily and weekly usage of selected apps like Instagram, TikTok, and YouTube. Users could voluntarily share their live total usage, percentage improvement, or goal-completion status with approved friends. Does Apple's Family Controls policy permit this? If not, is there an approved way to implement a friends leaderboard using Screen Time data? Thank you!
Replies
0
Boosts
0
Views
47
Activity
5d
Declared Age Range in sandbox: no sheet at launch, and the set per scenario
We are testing the Declared Age Range API with sandbox testers on an iPhone 17e with iOS 26.6.2 (Xcode 26.6, iOS 26.5 SDK). The app is not yet released; everything here is pre-release testing. We have filed three focused reports: FB25530441 (requestAgeRange returned .declinedSharing with no sheet), FB25530501 (the age that Age Assurance first shows at a sign-in against what the API reads), and FB25530513 (a selected scenario not reflected in requiredRegulatoryFeatures). Four questions remain that are not defects: When a sandbox tester has an Age Assurance scenario selected, should requestAgeRange present the sheet at launch, or answer from the scenario without showing one? Is there a way to see the sheet at launch in sandbox, as a first-time user would, so we can test the share and decline paths end to end? The article "Requesting people's age range information in your app" says the set's values "tell you which actions you need to take for compliance", and the sandbox page lists each scenario's age range, but we found neither saying which members each scenario produces. Please confirm: for each Age Assurance scenario, and for a tester with no scenario selected, what should requiredRegulatoryFeatures contain? Does the tester's App Store territory or creation date matter in sandbox? On 1 and 2. Our app calls requestAgeRange at launch when requiredRegulatoryFeatures contains .declaredAgeRangeRequired. On four days between October 31 and November 7, 2026, at every launch where we know it did make the request, Apple's age range sheet did not appear. Some requests we made by hand from a debug console returned the scenario's range with no sheet: on November 7, one on each of two testers on '13 - 15' returned a shared range of 13 to 15. One such request on October 31 did present the sheet; it is the only sheet on record across the four days (at a few launches the sheet was not written down separately). On 3. What we read on one tester, in this order, each scenario read before and after a relaunch unless noted: No scenario selected (signed in for the first time; Age Assurance showed no option selected), read after a relaunch only: none of the three members. '13 - 15, significant change approved', then '16 - 17, significant change declined', then 'Under 13, significant change approved': .declaredAgeRangeRequired and .significantAppChangeRequiresParentalConsent. '18+, age confirmed, significant change not applicable': .declaredAgeRangeRequired only. '18+, age confirmed, significant change applicable': .declaredAgeRangeRequired and .significantAppChangeRequiresAdultNotification. '18+, age not confirmed, significant change not applicable': .declaredAgeRangeRequired only. For these rows we read contains for the three members the iOS 26.5 SDK defines, so a member outside those three would not show. On November 5 we printed the whole set on 15 reads of sandbox testers, and no other member appeared.
Replies
0
Boosts
0
Views
69
Activity
1w
PDF Widget Annotations Disappear After Saving in PDFKit (including with Preview)
The Problem When a user toggles radio buttons or checkboxes in a PDF using Preview, the widgets disappear following subsequent interactions after the file is saved and reopened. This renders the form fields unusable. Steps to Reproduce the Problem Open a PDF with radio buttons or checkboxes in Preview. Toggle a radio button or checkbox. Save and close the file. Re-open the PDF in Preview. Toggle the same button again. The button (and any others with the same field name) will disappear. Expected Results Toggling a radio button or checkbox should update the field value without causing the button (or related buttons) to disappear. This behavior is consistent with previous versions of PDFKit. What is Happening In Preview, interacting with radio buttons and checkboxes correctly updates their appearance as expected. Saving the PDF, however, causes the appearance dictionary to reference a new N entry that is a single appearance stream unassociated with any state. The annotation's AS entry is not updated. The original N entry remains but is no longer referenced. Subsequent interactions fail to update the visual presentation because the appearance stream is missing. Impact on User Experience Radio buttons and checkboxes may disappear and become unusable when toggled. PDF documents become irreparably altered after a button is toggled and the file is saved. PDF file size significantly increases when the file is saved. Users may believe they have successfully completed a form, only for the data to become inaccessible or invisible to recipients. Forms may need to be completely restarted or recreated from scratch if the original becomes unusable. The corrupted PDF structure might cause the file to render incorrectly or crash in third-party PDF viewers. Affected Apps/OSs Tested with Preview 11.0 (1147), as well as other apps that use PDFKit, on macOS Golden Gate 27.0 (26A428). This problem also affects PDFKit on iOS 27.0 and iPadOS 27.0. Feedback/bug report: FB24866826 Related Sample Output Original PDF File Checkbox widget annotation (6 0 obj), its appearance dictionary (17 0 obj), and normal appearance dictionary (18 0 obj). Button is not checked. 6 0 obj << /Border [ 0 0 0 ] /Rect [ 90 390 110 410 ] /T (button1) /F 4 /Subtype /Widget /DA (/.AppleSystemUIFont 13 Tf 0 g) /MK 16 0 R /C [ 0 ] /AP 17 0 R /V /Off /M (D:20260919225320Z00'00') /AS /Off /FT /Btn /Type /Annot /Ff 0 >> endobj 17 0 obj << /N 18 0 R >> endobj 18 0 obj << /Yes 20 0 R /Off 22 0 R >> endobj PDF File after Save Checkbox widget annotation object (6 0 obj), its new appearance dictionary object (8 0 obj), a new normal appearance stream object (20 0 obj), and the original appearance stream dictionary (now 21 0 obj). File saved after user checked button. 6 0 obj << /Ff 0 /Type /Annot /AS /Off /AP 8 0 R /MK 9 0 R /C [ 0 ] /FT /Btn /M (D:20260919225320Z00'00') /DA (/.AppleSystemUIFont 13 Tf 0 g) /Subtype /Widget /F 4 /Border [ 0 0 0 ] /Rect [ 90 390 110 410 ] /T (button1) /V (Yes) >> endobj 8 0 obj << /N 20 0 R >> endobj 20 0 obj << /Filter /FlateDecode /Resources << /ColorSpace << /CS1 [ /ICCBased 29 0 R ] /CS2 [ /ICCBased 30 0 R ] >> >> /BBox [ 0 0 20 20 ] /Type /XObject /Subtype /Form /Length 123 >> stream x UéA ¬0 Ô}≈|†≈nà¢úÛÇ* —SA =}Ïr(»ñµ≤w◊€YËà’|ÙÎŒç'óRï∂#SäÏÌü∞¢S‰Ì§ôRÌX }–É•åY Éçˆ BŒ H " *â´8™ˆZø6z⁄ÿ ”ú6ɀ੠"∫t˘‹;'¬ endstream endobj 21 0 obj << /Off 22 0 R /Yes 23 0 R >> endobj Note: No object references 21 0 obj in the PDF.
Replies
5
Boosts
0
Views
1.1k
Activity
1w
PDF Widget Annotations appear Pixelated/Rasterized
The Problem On opening a PDF document in the Preview app, PDF widget annotations appear pixelated/rasterized. This problem exists with button, text, and choice widget subtypes. The pixelation becomes more apparent when zoomed in. Expected Results PDF widgets should appear sharp and smooth, without pixelation. In previous versions of the Preview app, widgets appear vector-based as expected. Impact on User Experience PDF widgets appear pixelated and inconsistent with text content in the same PDF document. Widgets do not look like elements of an interactive form but, instead, resemble low-quality embedded images. Affected Apps/OSs: Preview 11.0 (1147), as well as other apps that use PDFKit, on macOS Golden Gate 27.0 (26A428). A similar problem appears to affect PDFKit on iOS 27.0 and iPadOS 27.0 as well. Feedback/bug report: FB24843022
Replies
8
Boosts
3
Views
1.7k
Activity
1w
Declared Age Range: fallback behavior, cached results, and older iOS versions
Hello, I am preparing an 18+ workout logging app for iOS and would like to clarify the supported behavior of the Declared Age Range framework before completing its integration. Workout records, body measurements and saved videos are stored locally. Outside additional regulatory requirements, the planned entry flow uses a neutral adult self-declaration without collecting a date of birth or identity documents. The intended storefronts are Japan, the United States, the United Kingdom, Canada, Australia, New Zealand, Ireland and Singapore. These are implementation-design questions, not errors reproduced in a completed DAR integration. I am seeking documented API/platform behavior, not legal approval. Applicability checks that fail If isEligibleForAgeFeatures throws, returns notAvailable, or does not complete, is there a supported fallback signal or recommended retry strategy? I would not interpret an error as a successful “outside regulated scope” result. Is there a documented platform requirement for app access while applicability remains unresolved, separate from developers’ obligations under applicable law? Previously returned adult age ranges If declaredAgeRangeRequired applies and requestAgeRange fails after an earlier adult response, does Apple support relying on an app-stored result? I understand that the system caches responses; my question concerns a result stored separately by the app. Is there a supported way to detect when that result must be invalidated because of an Apple Account change, changes to age information, or sharing/consent changes? If no such signal exists, what implementation pattern does Apple recommend? I would not assume that a previous result always belongs to the current person or invent a cache lifetime. Earlier OS versions For affected newly created Apple Accounts in regulated regions, what supported path applies on: iOS versions without Declared Age Range; iOS 26.0–26.1, without isEligibleForAgeFeatures; iOS 26.2–26.3, without requiredRegulatoryFeatures? The age-assurance Q&A discusses existing Apple Accounts on iOS 18 or earlier. Is there additional documentation covering newly created affected accounts on earlier OS versions? While checks remain unresolved, the proposed design withholds advertising and new purchases and preserves existing data with free export. This is a proposed design, not an assumption that local recording is exempt from any requirement. References reviewed: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app Pointers to relevant documentation or sample code would be appreciated. Thank you.
Replies
0
Boosts
0
Views
41
Activity
1w