Search results for

“eskimo”

36,619 results found

Post

Replies

Boosts

Views

Activity

Reply to Notarization Requests In Progress
It seems that you’ve already seen my standard spiel about this. I’ve included it below, for the sake of others that stumble across this thread but also so I can quote it. [quote='819061021, AppDevObb, /thread/819061, /profile/AppDevObb'] What is causing my requests to always require in-depth analysis … ? [/quote] I’m not sure I’d put it that way. Rather, it’s that the system is taking its time to “learn how to recognise” you submissions. [quote='819061021, AppDevObb, /thread/819061, /profile/AppDevObb'] is there anything I can do to prevent it? [/quote] We have some advice on that topic in the “Q&A with the notary service team” that I reference in my standard spiel. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to rec
Topic: Code Signing SubTopic: Notarization Tags:
2w
Reply to Apple Silicon calling printf
Some more hints and tips in this space: The easiest way to determine the actual calling conventions for a given function is to create a small project in Xcode that calls the function and then looking at the resulting assembly. The Product > Perform Action > Assemble command is super helpful in that case. But you can also run the program and choose Debug > Debug Workflow > Always Show Disassembly [1]. Apple documents its calling conventions in Xcode > Application binary interfaces. This is basically Arm’s Procedure Call Standard with a few tweaks. And one of this tweaks affects varags. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] It says something about me that I have a hot key for that (-:
Topic: Programming Languages SubTopic: General Tags:
2w
Reply to Someone help me, i need to connect to wifi by scan a qrCode in my Flutter APP
Error 8 is .internal. This has come up on the forums a bunch of times, so I decided to write up my advice in Understanding NEHotspotConfigurationErrorInternal. [quote='819088021, Abel_Kefan, /thread/819088, /profile/Abel_Kefan'] Here's the logs: [/quote] That’s very hard to read. In future, please format such logs as a code block. See tip 5 in Quinn’s Top Ten DevForums Tips for advice on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Networking Tags:
2w
Understanding NEHotspotConfigurationErrorInternal
Error 8 in the NEHotspotConfigurationError domain is .internal, aka NEHotspotConfigurationErrorInternal. This error typically indicates that something went wrong in some sort of expected way, but we decided not to surface the exact cause [1]. This has come up a bunch of times before on the forums, and I have various titbits to share. To start, I want to address some specific cases: You’ll see this error if your app isn’t signed with the com.apple.developer.networking.HotspotConfiguration entitlement. To fix this, use Xcode’s Signing & Capabilities editor to add the Hotspot capability to your app. Historically developers reported a situation where once they encountered the error it would show up consistently, but then it would go away on restarting the device. If you see behaviour like that, that’s definitely a bug and I encourage you to file it as such. I have more about filing such bugs in Filing a Wi-Fi Bug Report. Of course, you have to wait to reproduce the error again before you’ll be able to file th
Topic: App & System Services SubTopic: Networking Tags:
0
0
60
2w
Filing a Wi-Fi Bug Report
Every now and again I end up helping a developer with a Wi-Fi issue. These fall into two groups: User-level Wi-Fi issues Development Wi-Fi issues A user-level Wi-Fi issue is one where the developer hasn’t created any of the products involved. An example of this is when you’re developing an app for an accessory and iOS is having problems connecting to that accessory but you don’t control the accessory’s firmware. In general, I recommend that you escalate such issues to the accessory vendor. They can then run their own investigation and, if necessary, file their own bug report. A development Wi-Fi issue is one that directly affects one of your products. For example, you’re developing a Wi-Fi accessory and iOS is having problems connecting to it. In that case, the onus is on you [1] to investigate why things are failing. If your conclusion is that iOS is behaving incorrectly, file a bug about that. IMPORTANT If you do file a bug in the context of some forums thread, please post your bug number to the thread, jus
Topic: App & System Services SubTopic: Networking Tags:
0
0
36
2w
Reply to Notarization submissions stuck "In Progress" for 10 days
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. ps I think this is now sorted out, bug please do reply here if you continue to have problems. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization Tags:
2w
Reply to Provisioning profile missing entitlement: com.apple.developer.icloud
My standard process for debugging problems like is: Test with a new project, with a completely different App ID. If that fails, something fundamental is wrong. But if it works, test with another new project, but this time using the sample App ID as your original project. If that fails, then the issue is tied to the code signing setup for that specific App ID. But if it works then you know the issue like in the main project itself. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
2w
Reply to Red "X" showing up for Certificates, Identifiers, & Profiles in xcode
[quote='879809022, FeiYehua, /thread/818161?answerId=879809022#879809022, /profile/FeiYehua'] Same problem for me [/quote] Is this for the same Apple Account you’re using to post here on the forums. If so, that Apple Account isn’t associated with any paid developer teams. If it’s some other Apple Account then you have a couple of options: You can either post here with that account so that I can check things based on that. Or if you can’t do that, seek formal help via Apple > Developer > Contact Us. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2w
Reply to XProtect makes app hang when running an AppleScript
Consider this: Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x0000000102c799bc This typically means that the app trapped, that is, it detected an internal error and deliberately crashed. For example, if you force unwrap an option that’s nil, you’ll trap like this. Now look at the backtrace: Thread 1 Crashed:: Dispatch queue: com.apple.root.utility-qos 0 DIM … 0x102c6c000 + 55740 1 DIM … 0x102c6c000 + 128212 2 libdispatch.dylib … _dispatch_call_block_and_release + 32 3 libdispatch.dylib … _dispatch_client_callout + 16 4 libdispatch.dylib … + 32 5 libdispatch.dylib … _dispatch_root_queue_drain + 736 6 libdispatch.dylib … _dispatch_worker_thread2 + 180 7 libsystem_pthread.dylib … _pthread_wqthread + 232 8 libsystem_pthread.dylib … start_wqthread + 8 frames 8 through 2 are Dispatch (GCD) machinery. Frame 1 is your code, which calls frame 0, which trapped. To learn more about this you need to symbolicate frames 1 and 0. See Adding identifiable symbol names to a crash report. Share
Topic: Privacy & Security SubTopic: General Tags:
2w
Reply to Crashed: com.apple.CFNetwork.LoaderQ
Again, I recommend that you review tip 5 of Quinn’s Top Ten DevForums Tips. Your reply above is barely readable. Focusing on the crash report, it comes from a third-party crash reporter. I don’t trust such reports in general. See Implementing Your Own Crash Reporter for a detailed explanation as to why. And in this specific case it doesn’t contain the information I need. I was hoping to get an Apple crash report, ideally one in JSON format. As to what’s happening here: com.apple.CFNetwork.LoaderQ is the name of the thread on which URLSession runs its core functionality. CFNetwork is calling down to Network framework. Which is, in turn, calling down to the QUIC implementation. That’s crashing for some reason, but it’s hard to offer any insight given the very limited information in this third-party crash report (it has no OS version, no binary image list, no register state, and so on). If you can find an Apple crash report for this, I’d be happy to take another look. Share and Enjoy — Quinn “The Eskimo
Topic: App & System Services SubTopic: Networking Tags:
2w
Reply to invalid API object reference
[quote='879858022, hasii2021, /thread/818406?answerId=879858022#879858022, /profile/hasii2021'] I set up the file system as APFS case-sensitive. [/quote] I’ve seen that cause problems in the past. However, I don’t think that’s the case here. I created a case-sensitive APFS disk image, copied your zip archive to that, and repeated my tests there, and everything still worked. But, yeah, a disk image is a great way to test stuff like this. If you managed to figure out what’s causing this, please reply here with the info. I’m super curious. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization
2w
Reply to Recording a Packet Trace
Do you work in a managed environment? I sometimes see reports like by folks who work in high-security industries, like health or finance. Their network, Mac, or device is locked down in some way that breaks this tooling. It’s hard to offer specific advice in that case, because these setups are very site specific, but I do have a few general hints: If you have a Mac laptop, you can relocate it to a different network. For example, you might run this test at home. Rather than running the proxy on your main work Mac, run it on a ‘victim’ Mac. For example, I often have great success using Mac-on-Mac virtualisation. Test with a victim ‘device’ that’s unmanaged. Or if you test device is managed, try a different device, like your own personal iPhone. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Networking Tags:
2w
Reply to Swift compiler fails in Release (-O) when using generic ObservableObject with @Published on iOS < 26 in Xcode 26.3
[quote='879813022, wuzihang, /thread/818722?answerId=879813022#879813022, /profile/wuzihang'] FB22081725 [/quote] Thanks for filing that. [quote='879813022, wuzihang, /thread/818722?answerId=879813022#879813022, /profile/wuzihang'] has [this] been routed to the appropriate Swift/Xcode engineering team … ? [/quote] Yes. [quote='879813022, wuzihang, /thread/818722?answerId=879813022#879813022, /profile/wuzihang'] [is] there is any information about which future Xcode version … ? [/quote] Even if there were, I can’t talk about The Future™ here on the forums. See tip 3 in Quinn’s Top Ten DevForums Tips. This lack of visibility is one of the reasons why I encourage folks with Swift compiler bugs to file their bugs via the Swift bug process. However, that’s not really appropriate here because you need an Apple framework, Combine, to reproduce it. But if you can find a way to reproduce the crash without that dependency, a Swift bug would make a lot of sense. ps In future, if you have existing case or feedback number
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2w
Reply to Using StoreKit from an AUv3 plugin that can be loaded in-process
[quote='879950022, timboudreau, /thread/818192?answerId=879950022#879950022, /profile/timboudreau'] the industry has produced plenty of ways to run untrusted code in-process [/quote] Sure. And if the only issue were the host not being able to trust the guest, such techniques might be feasible. But in this case you have to worry about the guest not trusting the host. [quote='879950022, timboudreau, /thread/818192?answerId=879950022#879950022, /profile/timboudreau'] can using StoreKit in an AUv3 work at all? [/quote] There’s an obvious way to make this work: Have the user run the app. Which uses StoreKit to check for the purchase. And stores the state in an app group, or keychain access group [1]. Which the app extension checks. This requires that the user run the app at least once so that it can achieve, but that’s not particularly onerous. However, the real question is really about whether your app extension can call StoreKit. I don’t know for sure. I’m gonna research this and get back to you. Share and Enjoy
Topic: Media Technologies SubTopic: Audio Tags:
2w
Reply to Notarization Requests In Progress
It seems that you’ve already seen my standard spiel about this. I’ve included it below, for the sake of others that stumble across this thread but also so I can quote it. [quote='819061021, AppDevObb, /thread/819061, /profile/AppDevObb'] What is causing my requests to always require in-depth analysis … ? [/quote] I’m not sure I’d put it that way. Rather, it’s that the system is taking its time to “learn how to recognise” you submissions. [quote='819061021, AppDevObb, /thread/819061, /profile/AppDevObb'] is there anything I can do to prevent it? [/quote] We have some advice on that topic in the “Q&A with the notary service team” that I reference in my standard spiel. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to rec
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
2w
Reply to Apple Silicon calling printf
Some more hints and tips in this space: The easiest way to determine the actual calling conventions for a given function is to create a small project in Xcode that calls the function and then looking at the resulting assembly. The Product > Perform Action > Assemble command is super helpful in that case. But you can also run the program and choose Debug > Debug Workflow > Always Show Disassembly [1]. Apple documents its calling conventions in Xcode > Application binary interfaces. This is basically Arm’s Procedure Call Standard with a few tweaks. And one of this tweaks affects varags. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] It says something about me that I have a hot key for that (-:
Topic: Programming Languages SubTopic: General Tags:
Replies
Boosts
Views
Activity
2w
Reply to Someone help me, i need to connect to wifi by scan a qrCode in my Flutter APP
Error 8 is .internal. This has come up on the forums a bunch of times, so I decided to write up my advice in Understanding NEHotspotConfigurationErrorInternal. [quote='819088021, Abel_Kefan, /thread/819088, /profile/Abel_Kefan'] Here's the logs: [/quote] That’s very hard to read. In future, please format such logs as a code block. See tip 5 in Quinn’s Top Ten DevForums Tips for advice on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Networking Tags:
Replies
Boosts
Views
Activity
2w
Understanding NEHotspotConfigurationErrorInternal
Error 8 in the NEHotspotConfigurationError domain is .internal, aka NEHotspotConfigurationErrorInternal. This error typically indicates that something went wrong in some sort of expected way, but we decided not to surface the exact cause [1]. This has come up a bunch of times before on the forums, and I have various titbits to share. To start, I want to address some specific cases: You’ll see this error if your app isn’t signed with the com.apple.developer.networking.HotspotConfiguration entitlement. To fix this, use Xcode’s Signing & Capabilities editor to add the Hotspot capability to your app. Historically developers reported a situation where once they encountered the error it would show up consistently, but then it would go away on restarting the device. If you see behaviour like that, that’s definitely a bug and I encourage you to file it as such. I have more about filing such bugs in Filing a Wi-Fi Bug Report. Of course, you have to wait to reproduce the error again before you’ll be able to file th
Topic: App & System Services SubTopic: Networking Tags:
Replies
0
Boosts
0
Views
60
Activity
2w
Filing a Wi-Fi Bug Report
Every now and again I end up helping a developer with a Wi-Fi issue. These fall into two groups: User-level Wi-Fi issues Development Wi-Fi issues A user-level Wi-Fi issue is one where the developer hasn’t created any of the products involved. An example of this is when you’re developing an app for an accessory and iOS is having problems connecting to that accessory but you don’t control the accessory’s firmware. In general, I recommend that you escalate such issues to the accessory vendor. They can then run their own investigation and, if necessary, file their own bug report. A development Wi-Fi issue is one that directly affects one of your products. For example, you’re developing a Wi-Fi accessory and iOS is having problems connecting to it. In that case, the onus is on you [1] to investigate why things are failing. If your conclusion is that iOS is behaving incorrectly, file a bug about that. IMPORTANT If you do file a bug in the context of some forums thread, please post your bug number to the thread, jus
Topic: App & System Services SubTopic: Networking Tags:
Replies
0
Boosts
0
Views
36
Activity
2w
Reply to Notarization submissions stuck "In Progress" for 10 days
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. ps I think this is now sorted out, bug please do reply here if you continue to have problems. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
2w
Reply to Provisioning profile missing entitlement: com.apple.developer.icloud
My standard process for debugging problems like is: Test with a new project, with a completely different App ID. If that fails, something fundamental is wrong. But if it works, test with another new project, but this time using the sample App ID as your original project. If that fails, then the issue is tied to the code signing setup for that specific App ID. But if it works then you know the issue like in the main project itself. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
Boosts
Views
Activity
2w
Reply to Red "X" showing up for Certificates, Identifiers, & Profiles in xcode
[quote='879809022, FeiYehua, /thread/818161?answerId=879809022#879809022, /profile/FeiYehua'] Same problem for me [/quote] Is this for the same Apple Account you’re using to post here on the forums. If so, that Apple Account isn’t associated with any paid developer teams. If it’s some other Apple Account then you have a couple of options: You can either post here with that account so that I can check things based on that. Or if you can’t do that, seek formal help via Apple > Developer > Contact Us. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
2w
Reply to XProtect makes app hang when running an AppleScript
Consider this: Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x0000000102c799bc This typically means that the app trapped, that is, it detected an internal error and deliberately crashed. For example, if you force unwrap an option that’s nil, you’ll trap like this. Now look at the backtrace: Thread 1 Crashed:: Dispatch queue: com.apple.root.utility-qos 0 DIM … 0x102c6c000 + 55740 1 DIM … 0x102c6c000 + 128212 2 libdispatch.dylib … _dispatch_call_block_and_release + 32 3 libdispatch.dylib … _dispatch_client_callout + 16 4 libdispatch.dylib … + 32 5 libdispatch.dylib … _dispatch_root_queue_drain + 736 6 libdispatch.dylib … _dispatch_worker_thread2 + 180 7 libsystem_pthread.dylib … _pthread_wqthread + 232 8 libsystem_pthread.dylib … start_wqthread + 8 frames 8 through 2 are Dispatch (GCD) machinery. Frame 1 is your code, which calls frame 0, which trapped. To learn more about this you need to symbolicate frames 1 and 0. See Adding identifiable symbol names to a crash report. Share
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
2w
Reply to Crashed: com.apple.CFNetwork.LoaderQ
Again, I recommend that you review tip 5 of Quinn’s Top Ten DevForums Tips. Your reply above is barely readable. Focusing on the crash report, it comes from a third-party crash reporter. I don’t trust such reports in general. See Implementing Your Own Crash Reporter for a detailed explanation as to why. And in this specific case it doesn’t contain the information I need. I was hoping to get an Apple crash report, ideally one in JSON format. As to what’s happening here: com.apple.CFNetwork.LoaderQ is the name of the thread on which URLSession runs its core functionality. CFNetwork is calling down to Network framework. Which is, in turn, calling down to the QUIC implementation. That’s crashing for some reason, but it’s hard to offer any insight given the very limited information in this third-party crash report (it has no OS version, no binary image list, no register state, and so on). If you can find an Apple crash report for this, I’d be happy to take another look. Share and Enjoy — Quinn “The Eskimo
Topic: App & System Services SubTopic: Networking Tags:
Replies
Boosts
Views
Activity
2w
Reply to invalid API object reference
[quote='879858022, hasii2021, /thread/818406?answerId=879858022#879858022, /profile/hasii2021'] I set up the file system as APFS case-sensitive. [/quote] I’ve seen that cause problems in the past. However, I don’t think that’s the case here. I created a case-sensitive APFS disk image, copied your zip archive to that, and repeated my tests there, and everything still worked. But, yeah, a disk image is a great way to test stuff like this. If you managed to figure out what’s causing this, please reply here with the info. I’m super curious. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization
Replies
Boosts
Views
Activity
2w
Reply to Recording a Packet Trace
Do you work in a managed environment? I sometimes see reports like by folks who work in high-security industries, like health or finance. Their network, Mac, or device is locked down in some way that breaks this tooling. It’s hard to offer specific advice in that case, because these setups are very site specific, but I do have a few general hints: If you have a Mac laptop, you can relocate it to a different network. For example, you might run this test at home. Rather than running the proxy on your main work Mac, run it on a ‘victim’ Mac. For example, I often have great success using Mac-on-Mac virtualisation. Test with a victim ‘device’ that’s unmanaged. Or if you test device is managed, try a different device, like your own personal iPhone. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Networking Tags:
Replies
Boosts
Views
Activity
2w
Reply to Swift compiler fails in Release (-O) when using generic ObservableObject with @Published on iOS < 26 in Xcode 26.3
[quote='879813022, wuzihang, /thread/818722?answerId=879813022#879813022, /profile/wuzihang'] FB22081725 [/quote] Thanks for filing that. [quote='879813022, wuzihang, /thread/818722?answerId=879813022#879813022, /profile/wuzihang'] has [this] been routed to the appropriate Swift/Xcode engineering team … ? [/quote] Yes. [quote='879813022, wuzihang, /thread/818722?answerId=879813022#879813022, /profile/wuzihang'] [is] there is any information about which future Xcode version … ? [/quote] Even if there were, I can’t talk about The Future™ here on the forums. See tip 3 in Quinn’s Top Ten DevForums Tips. This lack of visibility is one of the reasons why I encourage folks with Swift compiler bugs to file their bugs via the Swift bug process. However, that’s not really appropriate here because you need an Apple framework, Combine, to reproduce it. But if you can find a way to reproduce the crash without that dependency, a Swift bug would make a lot of sense. ps In future, if you have existing case or feedback number
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
2w
Reply to Using StoreKit from an AUv3 plugin that can be loaded in-process
[quote='879950022, timboudreau, /thread/818192?answerId=879950022#879950022, /profile/timboudreau'] the industry has produced plenty of ways to run untrusted code in-process [/quote] Sure. And if the only issue were the host not being able to trust the guest, such techniques might be feasible. But in this case you have to worry about the guest not trusting the host. [quote='879950022, timboudreau, /thread/818192?answerId=879950022#879950022, /profile/timboudreau'] can using StoreKit in an AUv3 work at all? [/quote] There’s an obvious way to make this work: Have the user run the app. Which uses StoreKit to check for the purchase. And stores the state in an app group, or keychain access group [1]. Which the app extension checks. This requires that the user run the app at least once so that it can achieve, but that’s not particularly onerous. However, the real question is really about whether your app extension can call StoreKit. I don’t know for sure. I’m gonna research this and get back to you. Share and Enjoy
Topic: Media Technologies SubTopic: Audio Tags:
Replies
Boosts
Views
Activity
2w
Reply to BGProcessingTask expirationHandler — No way to distinguish expiration reason
I don’t think so, but lemme double check and get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
Replies
Boosts
Views
Activity
2w