eskimo

[quote='872984022, ball-hayden, /thread/807938?answerId=872984022#872984022, /profile/ball-hayden'] I haven't had any other bug number given back to me [/quote] That FB number was what I was looking for. Thanks. I think you should have a read of Bug Reporting: How and Why? It’s full of information about how the bug reporting process works, including info about bug numbers. I also recommend that you read through Quinn’s Top Ten DevForums Tips. It’s my collection of hints and tips on how to use the forums effectively. Anyway, looking at FB21100266 I see it marked as a dup of an internal bug. That bug is being investigated by the Bluetooth engineering team, but I’ve no info to share beyond that. [quote='872984022, ball-hayden, /thread/807938?answerId=872984022#872984022, /profile/ball-hayden'] any suggestions of a workaround while this is fixed [/quote] I don’t know enough about Bluetooth to offer any insights into that. I’m gonna ping a colleague about it. However, if no one follows up here then you should assu

Thanks for closing the loop here. Memory management problems are such a pain. This problem started in CFNetwork, bounced through Core Animation and UIKit, and eventually found it’s way back to your code. That’s a great result, but it took a lot of effort. I think memory integrity enforcement, of which MTE is a part, holds great promise for finding these problems more easily. That tooling is only going to get better with time. And, hey, I was able to convince my boss than I needed an iPhone 17 to play with this stuff, so now I just need to find some time (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

OK. I was gonna ask if you were OK with this just being restricted to development-signed apps, but then I re-read your original post and saw this: [quote='812973021, naftaly, /thread/812973, /profile/naftaly'] I'm looking for something that could realistically be distributed to end users. [/quote] So, next question: Do you care if this is limited to devices with Developer Mode enabled? Or do you want it to work regardless of that? For context, there are two parts to your question: What’s currently possible? Would could Apple enable in the future? Your answers to these questions inform both parts. If you want to explore what’s currently possible, you need to realistic tests. If something works with a development-signed app on a Developer Mode device but your target audience is a distribution-signed app on all devices, that’s not a useful data point. In terms of The Future™, that’s not something I can address here. As I explain in tip 3 in Quinn’s Top Ten DevForums Tips, I encourage folks to file enhancement re

Background execution is tricky on iOS. I’ve collected together a bunch of links to useful resources in Background Tasks Resources. Specifically, make sure you read Testing and Debugging Code Running in the Background. [quote='813041021, mikeTheDad, /thread/813041, /profile/mikeTheDad'] I would like to use async/await and not have to experience the audio ending after just 15 seconds of the device screen being asleep. [/quote] You’re wrangling two completely separate axes of background execution here: Background audio URLSession Background audio is the most straightforward, at least conceptually: If your app supports background audio (UIBackgroundModes contains audio) and you start playing in the foreground, iOS will keep your app executing as it moves between the foreground and background as long as your app continues to play audio. Note I can only help you with the conceptual side of this. The actual mechanics of audio playback are outside my area of expertise. URLSession has two background execution models:

[quote='813148021, absinth, /thread/813148, /profile/absinth'] since this is cured by a reboot, lets ignore this issue [/quote] Well, it’d be good to get a bug on file about that. If you see it on a machine you control, please grab a sysdiagnose log before and after the restart and file a bug describing the issue with those logs attached. And please post your bug number, just for the record. Regarding your main issue, you wrote: [quote='813148021, absinth, /thread/813148, /profile/absinth'] the only thing that seems to be clear here is that this is a macOS 26 Tahoe bug. [/quote] That does seem likely. I’d like to get a bug on file about that too. So, something like this: Restart the Mac, just to clear away any cruft. Reproduce the problem, noting down the time. Grab a sysdiagnose shortly thereafter. File a bug with that sysdiagnose log, a general description of the problem, and the rough timestamp from step 2. Once you’re done, please post your bug number. If you want to dig into this yourself, you can do tha

[quote='813145021, thheidemann, /thread/813145, /profile/thheidemann'] Feedback Assistant report will be filed separately. [/quote] Thanks. And that’s definitely the best path forward for this. Please post your bug number when you’re done. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

What version of Xcode are you using here? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I can’t answer either of your direct questions, because of the reasons I outline in tip 3 in Quinn’s Top Ten DevForums Tips. But I can still offer some comments… To be clear, this isn’t a limit of Mac Catalyst specifically, but rather of the Mac itself. If and when Wi-Fi Aware is supported on the Mac, I’d fully expect it to be available to both normal and Catalyst apps. And if it isn’t, you could reasonably file a bug about that. As to when Wi-Fi Aware will arrive on the Mac, that’s in The Future™ and thus not something I can talk about. Normally I’d recommend that you file an enhancement request for this feature, but in this case I don’t think that’s necessary. The Wi-Fi Aware team is fully… ahem… aware of the desire for Wi-Fi Aware on macOS. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='813195021, CamJN, /thread/813195, /profile/CamJN'] that's a LOT of overhead! [/quote] In relative terms, sure. But it’s also a short amount of total time, so it doesn’t give you a lot of space to optimise. Anyway, there are a bunch of things you can do on this front, but there are also certain fundamental limits to how fast a given process can launch. If you use C to create a small ‘hello world’ project, how does its performance compare to that of your tool? 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 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. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='813222021, hkyoo@lguplus.co.kr, /thread/813222, /profile/hkyoo%40lguplus.co.kr'] is there a way to get MCC/MNC carrier codes on iOS? [/quote] No. Historically you could get this information from Core Telephony but that’s no longer the case. Are you working on behalf of a carrier? You tagged your question with Sign in with Apple. How does this question relate to that technology? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s focus this discussion on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='872931022, Leo_Nagano, /thread/812857?answerId=872931022#872931022, /profile/Leo_Nagano'] this is actually the first time I’m bringing up this NE system extension. [/quote] In that case I recommend that you switch to using Apple Development signing. Using Developer ID for day-to-day development is a bad idea in general, as I explained in that other post, but it causes significant grief in the case of NE system extensions: If you’re using Xcode, you run into the entitlement suffix issue you’ve noticed. For more on that, see Exporting a Developer ID Network Extension. The system requires that Developer ID-signed system extensions be notarised, so you have to notarise your app before each test O-: ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for all the extra info, but I’m still confused. Hotspot helper exists so that your app can participate in the process of authenticating with a hotspot network, that is, a Wi-Fi network where the user must interact with the network to gain access to the wider Internet. We call this out at the top level of the docs. I was hoping for an explanation of how your app uses the hotspot helper API to meet that goal. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

FYI, I’m helping a developer investigate a problem like this on another thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com