Post

Replies

Boosts

Views

Activity

BGTask expiry is never called for the requested BGTask.
We have a push-to-talk client, Part of Push APNS, app never received the BG task expiry. The app is suspended. Received Push-To-Talk APNS Here requested a BGTask and it got successfully registered Since it is a PTT call path, it ended immediately(via code) due to internal restrictions Ex: DND mode for client specific. The client allowed BG time more than 30 seconds and looks client has been suspended but Never received a BG task expiration handler from OS In sys diagnose logs confirmed, BGTask registered successfully 2024-09-03 16:18:47.331890 +0530 default AT&T EPTT : Created background task . But never got fired expiration handler. Feedback - FB15145380
3
0
218
Sep ’24
AudioOutputUnitStart failed with OSStatus error -50
Let the device is in locked screen Get incoming APNS video request to start video recording we are reporting this APNS to Callkit Accept incoming APNS request We are trying to initialise audio unit. Initialisation is success but starting is failing. Note - This issue is reproduced only if we receive video pull request in locked screen, after accepting callkit call we should not unlock the phone. If we unlock phone everything works as expected.
0
0
477
Jun ’24
PTT - PushToTalk - App Identifier Register
Hi there, I am trying to register for an App Identifier with the new PushToTalk Capability but getting the following message This request is forbidden for security reasons The selected team does not have a program membership that is eligible for this feature. If you need assistance, please contact Apple Developer Program Support. https://developer.apple.com/support We have enrolled for Annual Apple Developer Program Could you please help us in resolving this error.
2
0
1.2k
Jun ’22
CrashSymbolicator Script Failing to symbolicate the new JSON-format crash logs
As per Xcode 13 Release Notes - To support the new JSON-format crash logs generated in macOS Monterey and iOS 15, Instruments includes a new CrashSymbolicator.py script. This Python 3 script replaces the symbolicatecrash utility for JSON-format logs and supports inlined frames with its default options. For more information, see: CrashSymbolicator.py --help. CrashSymbolicator.py is located in the Contents/SharedFrameworks/CoreSymbolicationDT.framework/Resources/ subdirectory within Xcode 13. (78891800) usage: CrashSymbolicator.py [-h] [-d dSYM] [-s SEARCH_PATH] [-o OUTPUT_FILE] [-p] [-w N] [--no-inlines] [--no-source-info] [--only-missing] [--no-system-frameworks] [--no-demangle] [-v] LOGFILE Symbolicate a crash log python3 CrashSymbolicator.py -d PATH_TO_DSYMS -o PATH_TO_OUTPUT CRASH_LOG_FILE When we run this command getting the following errors Traceback (most recent call last): File "CrashSymbolicator.py", line 502, in symbolicate(args) File "CrashSymbolicator.py", line 482, in symbolicate crash_log.write_to(args.output, args.pretty) File "/Applications/Xcode.app/Contents/SharedFrameworks/CoreSymbolicationDT.framework/Versions/A/Resources/JSONCrashLog/JSONCrashLog.py", line 167, in write_to ips_header_dictionary = vars(self.ips_header) TypeError: vars() argument must have dict attribute
1
0
1.9k
Oct ’21