“eskimo”

Bugs like this crop up pretty frequently. There’s nothing your app can do to resolve them. The system is responsible for your updating your app; you’re not involved in that process at all. Given that, the only path forward is to file a bug explaining the exact circumstances under which you’re seeing the problem. Make sure to attach a sysdiagnose log taken immediately after the update fails. If possible, enable additional on the device before you start the test. Specifically, follow the App Store and VPN (Network Extension) instructions on our Bug Reporting > Profiles and Logs page. Please post your bug number, just for the record. Back in 2020 grtteja wrote: [quote='621100022, grtteja, /thread/654221?answerId=621100022#621100022, /profile/grtteja'] Are these bug reports publicly available [/quote] No. Bug reports that you file are only visible to you, other members of your team [1], and relevant folks at Apple. For general info on this whole process, see Bug Reporting: How and Why? A bug number is not in a

[quote='887433022, WangZiYuan, /thread/817264?answerId=887433022#887433022, /profile/WangZiYuan'] I've been a bit slack in keeping up with this issue. [/quote] No worries. I have plenty of other stuff to do (-: [quote='887433022, WangZiYuan, /thread/817264?answerId=887433022#887433022, /profile/WangZiYuan'] Could you teach me how to collect some logs? [/quote] Sure. But there’s not really much to say beyond what I wrote upthread: On the Mac that has the problem, enable additional logging per the VPN (Network Extension) for macOS instructions. Wait for the problem to occur. Immediately after, trigger the log capture. For iOS this would be triggering a sysdiagnose log, but for macOS the above-mentioned instructions describe a network-specific command. Then trigger a sysdiagnose log, just for good measure. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='887425022, iceboy, /thread/825789?answerId=887425022#887425022, /profile/iceboy'] it cannot be debugged. [/quote] Why is that? [quote='887425022, iceboy, /thread/825789?answerId=887425022#887425022, /profile/iceboy'] The same IPA file is installed on both this problematic device and the normally functioning devices. [/quote] How do you create that .ipa? The usual process for doing that is to export an Ad Hoc signed version of your app. If that’s the case then you can export a Development signed version from the some Xcode archive. At that point you have an exact some copy of the code that you can run and debug with Xcode. Just to be sure, you should check the keychain entitlements for each build. The .ipa is a zip archive under the covers, so you can change the extension to .zip and unpack it. Once you do that, dump the entitlements like so: % codesign -d --entitlements - /path/to/my.app Then use the same command to dump the entitlements of the Development signed version. Finally, compare the three ke

I fear this will never be triaged to reach the correct team. I’ll let you in on a little secret here. Even though my standard ‘file a bug’ text just say “for the record”, if you post your bug number I do a quick check that the bug is either with the right team or on its way to the right team. Of course that’s no guarantee that the team will act on the bug. Apple’s engineering teams have lots of competing demands on their time, and they set their own priorities in order to balance those demands. possibly ask for an AlarmKit category for it to reach them in future? You can request that directly by filing a bug against Feedback Assistant. And, yeah, you guessed it, please post your bug number, just for the record. 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

You’re using the term socket as a synonym for network connection. That’s not correct, and it muddies the waters when it comes to how to approach this problem. For example, one of your issues relates to connection viability, and the best way to handle that problem varies depending on whether you’re using the BSD Sockets API or the Network framework API. [quote='826000021, Gabriel_Heidemann, /thread/826000, /profile/Gabriel_Heidemann'] Is it possible to keep this TCP connection active in the background indefinitely on iOS while the user interacts with other apps? [/quote] No. See iOS Background Execution Limits. [quote='826000021, Gabriel_Heidemann, /thread/826000, /profile/Gabriel_Heidemann'] Invalid Outbound Data … My logs show strange character sequences (like gggggggggfdhj or vfgdddddddddddtty) being sent involuntarily. [/quote] It’s very unlikely that’s being generated by Network framework. The majority of times when I see problems like this it’s because the app itself is sending that junk, usually because

[quote='826119021, acabezasg, /thread/826119, /profile/acabezasg'] I have read the other recent stuck In Progress threads from new Developer IDs [/quote] You’ve probably seen my standard response to this, but I’ve included it below just in case other folks stumble across this thread. [quote='826119021, acabezasg, /thread/826119, /profile/acabezasg'] Could the queue be unblocked [/quote] The queue is not blocked. (When something actually goes wrong with notary, the forums light up like a Christmas tree.) [quote='826119021, acabezasg, /thread/826119, /profile/acabezasg'] or is there a team-side configuration that needs flipping? [/quote] It’s not that simple. I can’t offer detailed insight into the “in-depth analysis” case, but my experience, based on talking with many developers here on the forums, is that it usually clears in a day or two. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com You can expect that most uploads will

DevForums is primarily focused on Apple APIs and tools, so I can’t offer specific help with this issue. It’s possible that another third-party developer has seen this before and can help you. If not, I recommend that you seek help via the support channel for the library you’re using. However, I can address this: [quote='826107021, szigetics_nt, /thread/826107, /profile/szigetics_nt'] The problem seems to be that such keychain access groups access cannot be configured for Developer ID signed applications. [/quote] There’s a bunch to unpack here. First up, macOS has multiple keychain implementations. For the details, see TN3137 On Mac keychain APIs and implementations. Keychain access groups imply that you’re using the data protection keychain. Second, the data protection keychain is available to directly distributed programs that use Developer ID signing. See the intersection of the Keychain Sharing row and the Developer ID column in the table in Developer Account Help > Reference > Supported capabilitie

[quote='826040021, sidhantpande, /thread/826040, /profile/sidhantpande'] Investigation suggests newer Xcode beta versions now reject additional extended attributes beyond com.apple.FinderInfo during codesigning. [/quote] That’s not right. This check is applied by the codesign tool, not by Xcode. The codesign tool is part of macOS, not part of the developer tools, so updates to Xcode don’t change this behaviour specifically. It’s possible that an update to your OS has changed this, but that’s unlikely. What’s more likely is that other parts of your build system are causing this problem. [quote='826040021, sidhantpande, /thread/826040, /profile/sidhantpande'] Flutter tooling currently removes only: xattr -r -d com.apple.FinderInfo [/quote] This is the wrong way to resolve this issue. [quote='826040021, sidhantpande, /thread/826040, /profile/sidhantpande'] Replacing it with: xattr -cr successfully resolves the issue. [/quote] And this is just doubling down on the wrong approach. Rather, your should investigate w

[quote='887476022, George-J-E, /thread/817926?answerId=887476022#887476022, /profile/George-J-E'] FB22686646 [/quote] Thanks for filing that; it’s the best path forward for requests like this. 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='824713021, Sangeetha_G, /thread/824713, /profile/Sangeetha_G'] 1- Once we establish data path, Why iphone initiates data path termination instead using the same service for data path exchange. [/quote] Are you seeing this with the latest versions of iOS? So iOS 26.4.2 or the iOS 26.5 beta? The reason I ask is that the behaviour you’re seeing looks like an issue we fixed in iOS 26.4 where, after doing a pair setup, we would establish and then tear down a datapath. Given that you’re testing on iOS 26.2, it’s likely that this is the cause of the results you’re seeing. [quote='824713021, Sangeetha_G, /thread/824713, /profile/Sangeetha_G'] 2- Why do we go for PAIRING VERIFICATION everytime. [/quote] I believe that’s required by the Wi-Fi Aware spec. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

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. is it normal to not receive any response in the feedback assistant when there are known bugs found? Unless the folks investigating the issue need more info from your, they’ll only reach out via Feedback Assistant if and when an OS release with a fix starts seeding. For more background on how this process works, see Bug Reporting: How and Why? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m going to tackle a few of your issues now, and we can come back to the others once we’ve driven these to a conclusion. [quote='886912022, matteoq, /thread/821250?answerId=886912022#886912022, /profile/matteoq'] Glitch after successful login … is there any sort of known workaround/solution to this? [/quote] Not that I’ve seen. However, if you can reproduce this reliably then I encourage you to file your own bug with the details. Part of the issue with getting traction on FB12074874 is that it only reproduces in odd situations, at least IME. Please post your bug number, just for the record. [quote='886912022, matteoq, /thread/821250?answerId=886912022#886912022, /profile/matteoq'] Plugin update [/quote] It depends on the exact sequencing. When you’re at the login window, the system has already loaded your plug-in so updating it on disk doesn’t help. I typically update my plug-in when I’m logged in and then log out. The system will then pick up the new plug-in as part of bringing up loginwindow for the new se

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. I’ve done all of the above and still run into this issue. If you’ve eliminated your Mac, your iOS device, and your network, the one remaining environmental factor is your account. If you create a new test Apple Account, enroll it into the beta program, and use it to enable beta updates on your iOS device, do you still see the problem? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for the extra info. Does the problem reproduce with QAuthPlugins > LoginUIAuthPlugin? (I’m travelling right now so it’s hard for me to test this myself.) Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com