We have an iphone app that has an embedded webview using webkit, and we found the app crashes when we navigate to an specifc internal website. When I opened the ips file I see this stacktrace on the com.apple.main-thread WebCore::JSDOMRect::subspaceForImpl(JSC::VM&) WebCore::JSDOMRect::create(JSC::Structure*, WebCore::JSDOMGlobalObject*, WTF::Ref, WTF::DefaultRefDerefTraits>&&) WebCore::toJSNewlyCreated(JSC::JSGlobalObject*, WebCore::JSDOMGlobalObject*, WTF::Ref, WTF::DefaultRefDerefTraits>&&) JSC::JSValue WebCore::CloneDeserializer::readDOMRect() WebCore::CloneDeserializer::readTerminal() WebCore::CloneDeserializer::deserialize() WebCore::SerializedScriptValue::deserialize(JSC::JSGlobalObject&, JSC::JSGlobalObject*, WTF::Vector, WTF::DefaultRefDerefTrait WebCore::SerializedScriptValue::deserialize(JSC::JSGlobalObject&, JSC::JSGlobalObject*, WebCore::SerializationErrorMode, bool*) WebCore::SerializedScriptValue::deserialize(OpaqueJSContext const*, OpaqueJSValue const**) API::
Search results for
We are unable to process your request
69,585 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Thanks for the post. Your inquiry appears to pertain to a developer account and looks like you already talking to the developer Apple Support team that created those limits. I would recommend to file a enhancement request. If you'd like us to consider adding the necessary functionality, please file an enhancement request using Feedback Assistant. Once you file the request, please post the FB number here. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why? I trust you will achieve a favorable resolution. I extend my best wishes for your success. Albert Pascual
Worldwide Developer Relations.
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
Since we're talking about debuggers here, I just want to say that having DWARF (1) in your user name is excellent — thanks for the chuckle! As to attaching your custom debugger to a process with devicectl, this is not possible with the currently available commands provided by that tool. Our folks who work on the tooling around that command are interested in hearing what your needs are, so please send them some information on the type of functionality you need through Feedback Assistant. Once you've done that, please post the FB number here for reference. — Ed Ford, DTS Engineer (1): https://dwarfstd.org
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
With the latest (26) version of Apple's developer tools, is there a way to manually attach a debugger (other than lldb) to an iOS app launched with devicectl device process launch --start-stopped? In the past, this was possible via the ios-deploy third-party tool (now defunct), which provided a debugserver port. This information is notably missing when using devicectrl – although the process ID of the launch process is provided, and the tool is clearly aimed at letting you launch and attach to processes from the command line. lldb can, of course, attach via its built-in support for this using the device set of commands. But I'm explicitly looking for a way to attach my own debugger via the GDB-compatible debug proxy.
I have added an in-app purchase function into my app, and have enabled in-app purchase profile in developer portal(it's on by default and is marked gray in developer portal, I don't know if that's how it supposed to look like). I have issued the agreements and tried signing the app both manually and automatically, but neither of that worked. App can be built successfully in simulator but does not show the simulation window, but cannot build on real device or archive. Errors: Missing com.apple.developer.in-app-purchase, com.apple.developer.in-app-purchase.non-consumable, and com.apple.developer.in-app-purchase.subscription entitlements. Automatic signing failed Xcode failed to provision this target.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
StoreKit
App Store Connect
Provisioning Profiles
Just following up as I am still in need of a resolution. Quinn was handling this from the code/operation side, so wasn't really tracking this thread. However, there are two common issues here from the framework usage side. The first one is that by calling scheduleAppRefresh at app launch, you're unintentionally preventing your own task from reliably firing. Basically, here is what happens: Your app stopped running at some earlier point in the day for normal reasons (free up device memory, etc.). It came time to run your task, so the system launched your app. Your app started up, you configured the background task framework, then ran scheduleAppRefresh. scheduleAppRefresh scheduled your task to run 10 mins from now. Duet (the daemon that supports the background task framework) assessed your task state, determined that you had not tasks ready to run (since the next one isn't runnable for 10 min...) and suspended your app. Secondly, I think you probably want to use BGProcessingTask, NOT BGAppRefreshTask. These t
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags:
Hi, I have a couple questions about background app refresh. First, is the function RefreshAppContentsOperation() where to implement code that needs to be run in the background? Second, despite importing BackgroundTasks, I am getting the error cannot find operationQueue in scope. What can I do to resolve that? Thank you. func scheduleAppRefresh() { let request = BGAppRefreshTaskRequest(identifier: peaceofmindmentalhealth.RoutineRefresh) // Fetch no earlier than 15 minutes from now. request.earliestBeginDate = Date(timeIntervalSinceNow: 15 * 60) do { try BGTaskScheduler.shared.submit(request) } catch { print(Could not schedule app refresh: (error)) } } func handleAppRefresh(task: BGAppRefreshTask) { // Schedule a new refresh task. scheduleAppRefresh() // Create an operation that performs the main part of the background task. let operation = RefreshAppContentsOperation() // Provide the background task with an expiration handler that cancels the operation. task.expirationHandler = { operation.ca
I submitted for the first time my app and in app subscription together. do the subscriptions get approved separately? it seems like a loop. in the paywall of my app only for apple its failing to load payments/subscription info which im assuming to be the fact that my in app subscription didn't get approved yet, its currently waiting for review (first time submitting subscription). Meanwhile the app gets rejected multiple times because the reviewer can't seem to go beyond the paywall due to failure to load payments. Is this the similar experience anyone had? Do you have info that'd be helpful to give to the reviewers?
@neil95 This is great!! Thank you so much for this. I see you included a link to the code. I would recommend to zip it and upload it into the bug itself. You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label Resolution. We're unable to share any updates on specific reports on the forums. For more details on when you'll see updates to your report, please see What to expect after submission. I'll keep an eye out for issue and fix. Albert Pascual
Worldwide Developer Relations.
Topic:
UI Frameworks
SubTopic:
UIKit
I'm writing a program to control a PTZ camera connected via USB. I can get access to target camera's unique_id, and also other infos provided by AVFoundation. But I don't know how to locate my target USB device to send a UVC ControlRequest. There's many Cameras with same VendorID and ProductID connected at a time, so I need a more exact way to find out which device is my target. It looks that the unique_id provided is (locationID<<32|VendorID<<16|ProductID) as hex string, but I'm not sure if I can always assume this behavior won't change. Is there's a document declares how AVFoundation generate the unique_id for USB camera, so I can assume this convert will always work? Or is there's a way to send a PTZ control request to AVCaptureDevice? https://stackoverflow.com/questions/40006908/usb-interface-of-an-avcapturedevice I have seen this similar question. But I'm worrying that Exacting LocationID+VendorID+ProductID from unique_id seems like programming to implementation instead of interface.
Hello, I am in the process of implementing SharePlay support in my visionOS app. Everything runs fine when I test locally, but when my app is distributed via TestFlight, calling try await activity.activate() shows the SharePlay dialog as usual, but then when I start a new FaceTime call, my ImmersiveSpace gets dismissed. This is only happening when the app is distributed via TestFlight, when I run it locally the ImmersiveSpace stays active as expected. Looking at the console on my Mac I found this log: Invalid initial client settings class: UIApplicationSceneClientSettings; expected class: MRUISharedApplicationSceneClientSettings; bundle ID: com.apple.facetime; scene ID: com.apple.facetime:SFBSystemService-DDA8C751-C0C4-487E-AD85-59EF4E6C6050 Does anyone have an idea how I can fix this? It's driving me nuts and I wasted over a day looking for a workaround but so far been unsuccessful. Thanks!
Hi @arthurfromberlin Thanks for the response and detail. Can you attach a sysdiagnose to the feedback request? You can find instructions on how to capture a sysdiagnose here. The issue is tricky to debug since it only happens via TestFlight so the logs will help.
Topic:
Spatial Computing
SubTopic:
General
Tags:
I have tried everything and still I am getting this. Just for a test I created a new app (Master-Detail template Xcode 11.5) I have created an entry in the iTunes Connect to receive the app upon archiving and uploading. I regenerated all new certificates for iOS Development and Distribution. I created all new Provisioning profiles. The Dev profile builds deploys and runs on my device The Dist profile builds but when I select the distribution profile I get the Profile doesn't include the com.apple.application-identifier entitlement. error. When I download the profile within Xcode all looks good for the distribution profile: App ID: matches correctly Certificated: 1 Included includes the new signing certificate iPhone Distribution.... Capabilities: 3 Included Includes Game Center, In-App Purchase, and Keychain Sharing Entitlements: 5 Included Includes application-identifier, keychain-access-groups, beta-reports-active, get-task-allow, and com.apple.developer.team-identifier. Im not sure what is going on. This i
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
iOS
App Store
Entitlements
App Store Connect
Hello, my name is Kanazawa Kenta, and I am a university student currently conducting research and development using visionOS. In my project, I would like to access the main camera using the Enterprise APIs for visionOS. However, when I try to request permission or view the documentation, I receive the following message: Your account can’t access this page. There may be certain requirements to view this content. You must be the Account Holder of an Apple Developer Program for Organizations or an Apple Developer Enterprise Program to view this page. I am currently enrolled in the Apple Developer Program as an Individual. My question is: Is it possible to use the Enterprise APIs with an individual developer account? If not, what are the available options for students or researchers who wish to use these APIs for academic purposes? I would greatly appreciate any guidance or suggestions on how I can gain access, or alternative ways to use the main camera for research in visionOS. Thank you for your help.
Hello everyone, I'm facing a critical, blocking issue where my developer account (Team ID: K655PX7A46) is unable to generate a valid provisioning profile with the App Attest entitlement. I have confirmed this is a server-side issue and am hoping to get visibility from an Apple engineer who can investigate. The Problem: When I generate a provisioning profile for an App ID with the App Attest capability enabled, the resulting profile is defective. It is missing the required com.apple.developer.app-attest.environment key in its entitlements dictionary, causing Xcode to fail the build. What I Have Proven: The issue is not a misconfiguration. The App Attest capability is correctly enabled and saved on the App ID configuration page. The issue is not isolated to one App ID. I created a brand new App ID from scratch, enabled the capability during creation, and the server still generates a defective profile with the same missing entitlement. I have definitive proof by inspecting the downloaded .mobileprovisio
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Entitlements
Signing Certificates
App Attest
Code Signing