Search results for

İOS 26 beta battery %1

253,944 results found

Post

Replies

Boosts

Views

Activity

Reply to App Review Sign-In Information
Thank you for your post. We recommend that you sign up for a session with App Review during the weekly Meet with Apple event. Sign in with your Developer ID and select Request a one-on-one App Review consultation. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines.
1w
App Rejected Because No Approved Subscriptions — Stuck in a Review Loop (App & Plans Depend on Each Other)
Hi everyone, I’m currently stuck in a review loop related to in-app subscriptions and would really appreciate some advice. Here’s what’s happening: My app uses Apple’s in-app subscription system (auto-renewable). When I submit the app, it gets rejected because there are no active/approved subscription plans available for purchase. But the subscription plans themselves are also rejected or kept under review because the app isn’t approved yet. So I’m in a loop where: The app approval depends on the subscription approval, and the subscription approval depends on the app approval. I’ve been stuck in this situation for about a month now, and I can’t move forward. Here’s what I’ve tried so far: Displayed a message on the subscriptions screen saying that “No plans are available right now.” Displayed the plans as UI only, and when users try to subscribe, it shows a message like “Plans are currently under review, please try again later.” Despite these attempts, the app still gets rejected with the same reason — that t
1
0
64
1w
Navigation Bar Title Hidden When Right Bar Button Title Is Long (iOS 26)
I’m developing an app that includes a navigation bar with a centered title and a single right bar button item. I’ve noticed that when both the navigation bar title and the right bar button item’s title are relatively long, the navigation bar title becomes hidden. This issue only occurs on iOS 26. When running the same code on iOS 18, the layout behaves as expected, with both elements visible. Has anyone else experienced this behavior on iOS 26? Is this a known layout change or a possible bug?
1
0
386
1w
If you have code to package as a framework which has a 3rd party dependency, what can you do given that iOS doesn't support umbrella frameworks
I've got a large and complex app which has several dependencies upon 3rd party libraries (installed as pods). The app is structured according to Model-View-Controller design and there is a requirement to implement the Model part as an .xcframework so it can be included and used in the original app along with a few new apps. However, Apple documentation states that umbrella frameworks are not supported (Technical Note TN2435). The Model code has several dependencies which would be totally unfeasible to replace or remove, for example it uses RealmSwift for database storage. Obviously it would be impossible to write one's own database storage scheme in place of using Realm. However, if my framework uses Realm as a dependency, then its now become an umbrella framework. So therefore not supported according to Apple documentation. So what are options/solutions?
11
0
523
1w
Reply to If you have code to package as a framework which has a 3rd party dependency, what can you do given that iOS doesn't support umbrella frameworks
Above I wrote: [quote='844753022, DTS Engineer, /thread/776743?answerId=844753022#844753022'] if you rename your copy of WVPWaffle to FORWaffle, then you’re all good [1] [/quote] That footnote called out some caveats, but on reviewing this thread today I remembered another one. It’s not uncommon for a library to use global resources. In the posts above I talked about one really important one, namely the Objective-C class namespace. However, there are more. For example, imagine a framework that does this: let b = Bundle(identifier: com.example.WaffleVarnishPro)! … access resources via `b` … IMPORTANT Frameworks shouldn’t do this. A better option is to use Bundle(for: SomeClass.self) or #bundle. However, the fact that they shouldn’t do this doesn’t mean that they don’t. This touches on another global resource, namely the bundle ID namespace managed by Bundle. So, if you decide to take the “rename the types” path I outlined above, that might not be sufficient. It’s possible th
1w
Reply to XCFramework with Common Third-Party Dependencies Causing Duplicate Symbol Conflicts
There isn’t a great answer to this in the general case. Ignore the build-time issue right now, and focus on the run-time one: Imagine an app A which depends on F. It also links to a library L which depends on F. The process running A can’t load two different copies of F [1]. Which means L must use a specific version of F, and A must agree to use the same version. If F supports ABI compatibility then you can resolve this conundum by having A embed the newest version of F. But not all frameworks support ABI compatibility. IMPORTANT ABI compatibility has both technical and social aspects. You can’t tell just by looking at the framework whether it’ll be ABI compatible in the long term. You’ll also need a promise from the framework author. Coming back to the build side of this, that presents significant practical challenges: [quote='805901021, Charita, /thread/805901, /profile/Charita'] Static linking: Google Maps symbols compiled into my binary [/quote] Don’t do that. It’ll result in two copies
1w
Keyframe animation crashes with +[_SwiftUILayerDelegate _screen]: unrecognized selector sent to class on iOS 26
We have an UIViewController called InfoPlayerViewController. Its main subview is from a child view controller backed by SwiftUI via UIHostingController. The InfoPlayerViewController conforms to UIViewControllerTransitioningDelegate. The animation controller for dismissing is DismissPlayerAnimationController. It runs UIKit keyframe animations via UIViewPropertyAnimator. When the keyframe animation is executed there’s an occasional crash for end users in production. It only happens on iOS 26. FB Radar: FB20871547 An example crash is below. Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Reason: +[_SwiftUILayerDelegate _screen]: unrecognized selector sent to class 0x20c95da08 Termination Reason: SIGNAL 6 Abort trap: 6 Triggered by Thread: 0 Last Exception Backtrace: 0 CoreFoundation 0x1a23828c8 __exceptionPreprocess + 164 (NSException.m:249) 1 libobjc.A.dylib 0x19f2f97c4 objc_exception_throw + 88 (objc-exception.mm:356) 2 CoreFounda
2
0
222
1w
Reply to Keyframe animation crashes with +[_SwiftUILayerDelegate _screen]: unrecognized selector sent to class on iOS 26
We have the same problem with iOS26 - thousands of crashes in the production. iOS 18 and older works just fine. We are not able to reproduce it locally. It started with building our app with xcode 26, with older xcode it woks ok even on iOS 26, but we were unable to do iOS 26 specific code. Fatal Exception: NSInvalidArgumentException +[_SwiftUILayerDelegate _screen]: unrecognized selector sent to class 0x1efa9da08 0 CoreFoundation 0xc98c8 __exceptionPreprocess 1 libobjc.A.dylib 0x317c4 objc_exception_throw 2 CoreFoundation 0x1656cc -[NSObject(NSObject) doesNotRecognizeSelector:] 3 CoreFoundation 0x464f8 ___forwarding___ 4 CoreFoundation 0x4e3a0 _CF_forwarding_prep_0 5 UIKitCore 0x18e7880 __35-[UIViewKeyframeAnimationState pop]_block_invoke 6 CoreFoundation 0x12170 __NSDICTIONARY_IS_CALLING_OUT_TO_A_BLOCK__ 7 CoreFoundation 0x1a47cc -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] 8 UIKitCore 0x18e76bc -[UIViewKeyframeAnimationStat
Topic: UI Frameworks SubTopic: UIKit Tags:
1w
Reply to How to use the WebAssembly (wasm) binary module in macos App
Yeah, I figured you’d get see something like this. IMPORTANT All of the following assumes you’re targeting macOS. The story for iOS and its child platforms is very different. From the perspective of code signing on Apple platforms, this is data not code. We touch on this in Placing content in a bundle; see the discuss of shell scripts in that doc. Given that, you should place these files in Contents/Resources where they’ll be sealed over by the code signature like any other resource file. That takes care of the on-disk side of things. How you handle this in memory depends on your WebAssembly runtime. Some runtimes are pure interpreters. Those don’t generate code on the fly, and thus don’t need to take any special action to allow that code to run. However, high-performance WebAssembly runtimes often include a JIT. There are two ways you can create a JIT: The recommended path is the one described in Porting just-in-time compilers to Apple silicon. Many legacy JITs don’t follow those rules, rel
Topic: Code Signing SubTopic: Notarization Tags:
1w
Reply to Icon Composer and Xcode building time
Hi, I'm seeing the same thing. I want to use AlternateAppIcon, so I added 7 AppIcon-x.icon files to my project in Xcode 26, and these icon files are created by icon composer software. And I also see the AssetCatalogSimulatorAgent(370% CPU). Finally, it took 30mins to build succeeded project. Very slowly. What should I do?
1w
DriverKit IOUserSerial Driver
Hello everyone. After a lot of research and some tests from various sources, I have actually built a small SerialDriverKit IOUserSerial driver. Unfortunately, the documentation on the official sites is tight-lipped and very thin. At least I have a running driver instance. Now my request and question: Can anyone give me a tip on how to get the data from the serial client? I have already called IOUserSerial::ConnectQueues(...) in the IOUserSerial::Start() method and I got the IOMemoryDescriptors for interrupt, RX and TX to my driver instance. I tried to get access to the memory in the method IOUserSerial::TxDataAvailable() with IOMemoryDescriptor::CreateMapping(...). Unfortunately, no data is coming in. It's always 0x00. Here is the OS log: kernel: (org.eof.tools.VSPDriver.dext) kernel: (org.eof.tools.VSPDriver.dext) [VSPDriver] init called. kernel: (org.eof.tools.VSPDriver.dext) [VSPDriverPrivate] constructor called. kernel: (org.eof.tools.VSPDriver.dext) [VSPDriver] start called. kernel: (org.eof.tools.VSPDri
19
0
1.1k
1w
Core Bluetooth and app background launch
TN 3115 states that apps that do not use AccessorySetupKit will loose the ability to launch into the background to service bluetooth in iOS26. Starting in iOS 26 and iPadOS 26, only apps that use AccessorySetupKit to setup Bluetooth accessories will be relaunched. Is there any more information regarding this? Will it affect any app under iOS26 or only those build against the iOS26 SDK? My app (dev build) is still relaunched, even though I'm running iOS26, so I wonder if there are any more conditions checked.
1
0
43
1w
Reply to Core Bluetooth and app background launch
You seem to have misunderstood. That note, Note 5, only pertains to the specific cases where Note 5 is referred to, namely: if the app Force Quit by the user Control Center Bluetooth button toggled An app that was force quit was never able to be relaunched before. iOS 26 actually adds the capability for such apps to be launched if they opt in to use AccessorySetupKit. So, this is not a case of apps losing the capability to relaunch, but a case of apps gaining the capability to relaunch in cases where they weren't able to before, if they use AccessorySetupKit.
Topic: App & System Services SubTopic: Core OS Tags:
1w
Migration Subscription API returns 500 error
We got Advanced Commerce API and the generic product identifiers approved. When I was try to migrate a sandbox subscription to ACA enabled subscription I hit an error Request payload (Hid some info but the requestReferenceId is the real) { descriptors: { description: Migrated, displayName: Migration }, items: [ { sku: product_1mo_999, description: description, displayName: Product } ], requestInfo: { requestReferenceId: 3b0b8e67-d8a0-45f4-8f6d-06bffa9a2c08 }, storefront: USA, targetProductId: com.company.generic.subscription, taxCode: C003-00-1 } Response { errorCode: 5000000, errorMessage: An unknown error occurred. }
4
0
205
1w