“eskimo”

It’s hard to give definitive advice here because there are many different ways to do these things. But lemme take a stab at your two main questions: [quote='831836021, Yoorbo, /thread/831836, /profile/Yoorbo'] When sharing SwiftUI views and business logic for DRY, whats the actual best way to do that? A „core“ swift package, or a library? [/quote] One of those, yes. [quote='831836021, Yoorbo, /thread/831836, /profile/Yoorbo'] what are the implications of choosing one over the other? [/quote] If your library is only ever going to be used by an Xcode project then I think a framework target makes more sense. Swift packages do have significant advantages, but framework targets are directly implemented by Xcode and thus tend to work better when you’re building an app for Apple platforms. [quote='831836021, Yoorbo, /thread/831836, /profile/Yoorbo'] I’ll have to use app groups so that both can have the same data store [/quote] Right. Technically what you use is an app group container. You sign your app to claim acce

What specific API are you using? The Multipeer Connectivity framework? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The best place for this sort of feedback is Feedback Assistant. If you reply here with your bug number, I’ll make sure it gets seen by the right folks. ps Make sure to include info about your browser and screenshots that illustrate the concern. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This is very reminiscent of another thread I’ve been working recently. Are you on the same team as Hitesh_Reddy? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='831868021, smadsen_om, /thread/831868, /profile/smadsen_om'] Filed a feedback on this: FB23038153 [/quote] Thanks. Our current thinking is that installing Xcode 27 beta installed a version of MobileDevice that broke compatibility with earlier releases. Unfortunately it’s hard to revert that. So I’m not sure what the best path forward is here. I’m going to research this and get back to you, possibly next week after the WWDC dust has settle a bit. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The Network framework reached out to me to let me know that they’re already tracking this issue (r. 171639997). They hope to fix it sooner rather than later, but I’ve no concrete timeline to share. 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='890962022, xingkaixin, /thread/829603?answerId=890962022#890962022, /profile/xingkaixin'] This is why I suspect there may be an issue beyond normal processing delays. [/quote] You are correct on that front. This behaviour is strongly indicative of the “in-depth analysis” I mentioned above. Your oldest request is now 3 days old, which seems like a long time but isn’t completely out of the ordinary. If it’s still stuck after a week, reply back here and I’ll dig deeper. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='890660022, KayleeSC, /thread/791352?answerId=890660022#890660022, /profile/KayleeSC'] This new problem only affects the App Store version of my app [/quote] Well, that’s not good. For problems like this — where a working app fails on an early beta release — it’s best to go straight to Feedback Assistant. Please post your bug number, just for the record. ps You might want to consider putting your next follow-up in a new thread. Forums is happier with more, shorter threads. And as long as you use the same subtopic and tags as this thread, I’ll see it go by. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='890367022, soykanozcelik, /thread/829387?answerId=890367022#890367022, /profile/soykanozcelik'] i am not developing my app via Xcode [/quote] Understood. But when you’re developing for iOS there’s no way to avoid the Xcode infrastructure, and I’m trying to distinguish between these two cases: Your Xcode setup has a problem. Your third-party tooling has a problem. I can’t help you with the latter, but if the test I suggested up thread shows a problem with Xcode, I can help you with that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='890297022, RomainDropB, /thread/827228?answerId=890297022#890297022, /profile/RomainDropB'] The trailing URL problem was indeed our issue [/quote] Oh, cool. Regarding your follow-up question, can you put that in a new thread? If you use the same subtopic and tags as this thread, I’ll be sure to see it go by. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for filing FB22931581. You should check whether the affected machines have an Endpoint Security client installed on them. That’s a common source mysterious EPERM errors like this. If so, ask the customer to (temporarily) disable the ES client and try again. If that resolves this issue, that gives you a new avenue to explore. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='890294022, Altair4Ru, /thread/826325?answerId=890294022#890294022, /profile/Altair4Ru'] Doesn't the fact that it happens only on certain latest iPadOS versions prove than iPadOS is giving us less? [/quote] It’s strong evidence, but it’s not conclusive. For example, if the suballocator was specific tuned to match the behaviour of the system allocator, and then the system allocator changed, that could result in memory fragmentation that only causes problems when that combination in play. So, my advice is to measure rather than that assume. [quote='890294022, Altair4Ru, /thread/826325?answerId=890294022#890294022, /profile/Altair4Ru'] I believe enabling it has some drawbacks [/quote] The main drawback is that the kernel has to allocate more memory to keep track of your large address space. OTOH, it’d be interesting datapoint. You could, for example, ship a beta release this with enabled and then compare the crash rate on that versus that of the previous beta. That would at least confirm that address spac

You posted this during our Networking Q&A, so I had a chance to talk about it with an eSIM expert. Unfortunately we don’t have a quick answer for you. It’s hard to offer insight based on the very limited info we have here. Also, this is kinda off-topic for the Apple Developer Forums. This is about the user-level behaviour of your iPhone, not about the APIs that developers use to create apps. My advice is that your ask this over on Apple Support Community, run by Apple Support, to see if anyone over there has any suggestions. Or, failing that, and assuming you want to spend more time on this, you could contact Apple Support directly. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m not aware of any definitive user- or admin-facing docs about WAB. Honestly, I suspect this isn’t an accident, in that WAB is rarely deployed. Regardless, the path forward is clear: If you want better docs, you should file an enhancement request for those docs. IMPORTANT Don’t file your ER against the developer documentation, because such information would come from the customer-facing docs folks. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com