Search results for

show when run

112,670 results found

Post

Replies

Boosts

Views

Activity

Reply to CXCallUpdate not working for outgoing calls
I try to update remoteHandle using CXCallUpdate for outgoing calls, but this works only on iOS 15 but not on 17 or 18 (16 didn't test). What's actually not working here? Are you looking at what the lock screen UI shows or what you see in other locations (particularly in the Recent call list)? There is a longstanding issue (r.126348631) where call updates aren't being displayed on the lock screen interface; however, this is purely about UI showing old data, not about the update itself completely failing. Notably: I use this handle value to implement recall by tapping on a call in the Recents tab of the system address book. But since my calls can transform from p2p to group calls, I need to update the handle value or find some other way to pass call identification info. ...I'd expect this sort of thing to work exactly the way you need/expect, regardless of what the lock screen UI shows. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic: App & System Services SubTopic: General Tags:
3d
Metal 4: When is it ok to dealloc a MTLBuffer's memory
I have something like this drawing in an MTKView (see at bottom). I am finding it difficult to figure out when can the Swift-land resources used in making the MTLBuffer(s) be released? Below, for example, is it ok if args goes out of scope (or is otherwise deallocated) at point 1, 2, or 3? Or perhaps even earlier, as soon as argsBuffer has been created? I have been reading through various articles such as Setting resource storage modes Choosing a resource storage mode for Apple GPUs Copying data to a private resource but it's a lot to absorb and I haven't been really able to find an authoritative description of the required lifetime of the resources in CPU land. I should mention that this is Metal 4 code. In previous versions of Metal, the MTLCommandBuffer had the ability to add a completion handler to be called by the GPU after it has finished running the commands in the buffer but in Metal 4 there is no such thing (it it were even needed for the purpose I am interested in). Any advice and/or pointe
2
0
136
3d
Reply to DCAppAttestService errors: com.apple.devicecheck.error 3 and 4
Error 3 is invalidKey. Under normal circumstances, you receive this error if something goes wrong with generating or retrieving the attestation key. Unfortunately due to a bug, there are some instances, where a user's instance of the app will constantly fail. If these subset of users have had their phones since iOS 17.0 or earlier, this would be explained by a known bug in earlier versions of iOS, which impacts an underlying dependency of DCAppAttestService and is fixed in iOS 17.1. While we don’t expect any new issues popping up from this point on, unfortunately any device that got stuck in this state from before 17.1 will not be automatically cleared. While there might be actions for the users to clear this error state, experience taught us that they are just as likely to make matters worse, so we are no longer recommending developers to reach out to their customers to resolve the issue. One solution would be to treat any app instance in this state which is running on an earlier iOS, or persistentl
Topic: Privacy & Security SubTopic: General Tags:
3d
CoreBluetooth Advertiser role CBPeripheralManager didSubscribeToCharacteristic: not getting invoked on iPhone 17 Air/Pro (iOS 26.1+)
When using CBPeripheralManager in the peripheral role on iPhone 17 series devices (iPhone 17 Air, iPhone 17 Pro) running iOS 26.1 and above, the delegate method peripheralManager:central:didSubscribeToCharacteristic: is never called when a third-party BLE central device attempts to connect and subscribe to a characteristic. This functionality works correctly on all previous iPhone models and iOS versions. (This worked previously for the same iPhone 17 Air/Pro when running iOS 26.0.1.)
1
0
36
3d
Reply to CoreBluetooth Advertiser role CBPeripheralManager didSubscribeToCharacteristic: not getting invoked on iPhone 17 Air/Pro (iOS 26.1+)
If this is was working before and broke with 26.1, you should file a bug report on this after making sure that the latest iOS 26.2 has not First we need a Bluetooth diagnostic log. Please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Bluetooth for iOS to install a logging profile on your device. Then, once the logging profile is installed: reproduce the problem, keeping track of the actual time of the actions you take and the result you see. if you can, also include a sniffer log of the same. Please include the actual log, and an ASCII export of it from the logger. make sure there aren’t any extraneous BLE devices around, and no other apps are trying to connect to some other BLE device while you are conducting this test. Once the problem is reproduced, follow the instructions at the above link to trigger a sysdiagnose If you are able to run the same test on a device that is still on an iOS version without the issue, please run the test the
Topic: App & System Services SubTopic: Core OS Tags:
3d
Reply to "canOpenURL:" on a thread that isn`t main thread?
Thanks for the post, can you provide a little more information about the URL you are passing or just the code you are using when that message shows in your console? As that API can be called in a thread that is not the main thread as shows in the documentation: You can call this method safely on a thread that isn’t the main thread. https://developer.apple.com/documentation/uikit/uiapplication/canopenurl(_:) Interesting to see what URL are you calling, the method should return a true or false only. Providing a focused sample and iOS version, Xcode and macOS is always a good idea. Thanks Albert Pascual
  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: UIKit Tags:
3d
"canOpenURL:" on a thread that isn`t main thread?
When I call this method on a thread that isn`t thread. And chose main thread check on target, The Console show the world : Main Thread Checker: UI API called on a background thread: -[UIApplication canOpenURL:] PID: 8818, TID: 10191278, Thread name: (none), Queue name: com.myqueue.canopen, QoS: 0 Backtrace: 4 TestDemo 0x0000000102f6c068 __39-[AppTools isExists:]_block_invoke_3 + 892 5 CoreFoundation 0x000000019e22995c 7519E999-1053-3367-B9D5-8844F6D3BDC6 + 1042780 6 CoreFoundation 0x000000019e12ec98 7519E999-1053-3367-B9D5-8844F6D3BDC6 + 15512 7 TestDemo 0x0000000102f6bba0 __39-[AppTools isExists:]_block_invoke_2 + 424 8 libdispatch.dylib 0x0000000103a4d7fc _dispatch_call_block_and_release + 24 9 libdispatch.dylib 0x0000000103a4ebd8 _dispatch_client_callout + 16 10 libdispatch.dylib 0x0000000103a55b48 _dispatch_lane_serial_drain + 744 11 libdispatch.dylib 0x0000000103a566e4 _dispatch_lane_invoke + 448 12 libdispatch.dylib 0x0000000103a61adc _dispatch_workloop_worker_thread + 1324 13 libsystem_pthread
2
0
67
3d
Making sure uploads continue in background, but also works in foreground
Hello! I have read most of the Background Tasks Resources here https://developer.apple.com/forums/thread/707503 - but still have a few questions that I need clarified. To provide our context, our usecase is that our user wants to upload files to our servers. This is an active decision by the user to initiate the upload, but we also want make sure the files are uploaded, even if the user chooses to background our app. If we use a URLSession.backgroundto initiate the uploadTask, I understand that we are passing it of to the urlsession deamon to handle the upload. Which is great, if the user chooses to background our app. But, what if they just stay with the app in the foreground? Will it start uploading immediately? Can we expect the same latency that a standard URLSession will provide? And the potential delay will only occur if they actually background our app. Also, what happens if a background upload is in-progress and the user enters our app again? Will it gain priority, and run with similar latenc
1
0
76
3d
Reply to Making sure uploads continue in background, but also works in foreground
[quote='812219021, madsodgaard, /thread/812219, /profile/madsodgaard'] I have read most of the Background Tasks Resources here [/quote] Cool. But there are some network specific ones you should also read: Moving to Fewer, Larger Transfers Testing Background Session Code The first one is probably most relevant to your issue. Networking Resources has these links and a lot more. [quote='812219021, madsodgaard, /thread/812219, /profile/madsodgaard'] But, what if they just stay with the app in the foreground? Will it start uploading immediately? [/quote] I would expect so. However, that’s not guaranteed. The nature of background sessions is that the system gets to choose when to run the transfer, based on its global view of the device state. IMPORTANT A lot of this stuff is not documented, and deliberately so. These policies are considered to be implementation details. They’ve changed in the past and it wouldn’t surprise me if they changed again in the future. So, when you ask “Will it do X?” the only rea
3d
Getting a basic URL Filter to work
I haven’t been able to get this to work at any level! I’m running into multiple issues, any light shed on any of these would be nice: I can’t implement a bloom filter that produces the same output as can be found in the SimpleURLFilter sample project, after following the textual description of it that’s available in the documentation. No clue what my implementation is doing wrong, and because of the nature of hashing, there is no way to know. Specifically: The web is full of implementations of FNV-1a and MurmurHash3, and they all produce different hashes for the same input. Can we get the proper hashes for some sample strings, so we know which is the “correct” one? Similarly, different implementations use different encodings for the strings to hash. Which should we use here? The formulas for numberOfBits and numberOfHashes give Doubles and assign them to Ints. It seems we should do this conversing by rounding them, is this correct? Can we get a sample correct value for the combined hash, so we can ve
29
0
1.6k
3d
Validation failed (-19241) The app contains one or more corrupted binaries. Rebuild the app and resubmit.
I am using XCode (Version 26.0.1 (17A400)) -> Archive -> Distribute App (or Validate App) to upload my iOS app into App Store Connect. However I am always getting this error: Uploading SPI errors: Validation failed (409) The app contains one or more corrupted binaries. Rebuild the app and resubmit. NSUnderlyingError : Validation failed (-19241) The app contains one or more corrupted binaries. Rebuild the app and resubmit. code : STATE_ERROR.VALIDATION_ERROR I tried exporting the app as an IPA and uploading with Transporter, but I see the same error. I couldn't find any other useful logs or error messages. More info: I have created the app in App Store Connect and this is my first time uploading. The app can build and run on my physical phone and emulator without any problem. Would be great to get some help! Thanks!
2
0
197
3d
Reply to Error while AppStore Connect Upload
So one of the following must be true: You want to use the Background Tasks framework to run long-running tasks via BGProcessingTask. Or you don’t. If you do, add the BGTaskSchedulerPermittedIdentifiers property to your Info.plist and populate it with the list of background task identifiers you use. If you don’t: Remove the processing value from the UIBackgroundModes property in your Info.plist. Remove any code that uses BGProcessingTask. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
3d