Post not yet marked as solved
It seems that you can now do the one handed zoom gesture in MapKit that you've been able to do for some time in the Maps app. For those not familiar this is a tap and then tap again. On the second tap hold your finger on the screen and you can move up and down to control zoom. It's quite nice but now it's in MapKit it is causing issues!Many apps have a lot of annotations, unlike the Maps app. It seems that tapping on an annotation and then trying to pan around actually triggers this new zoom action! All I was trying to do was pan!Is there any way to disable this new one handed zoom or can it be tweaked by Apple before launch as it is behaving not how a user would expect!
Post not yet marked as solved
Hello,
We got invited to the Xcode Cloud beta and I added one of our projects.
It looks like the archive succeeds but it always reports an error.
How can I get this looked at?
Thank you
Post not yet marked as solved
At the moment we have an auto renewing subscription and we use the original_transaction_id as a marker in our database.
If we turn on Family Sharing it was mentioned that each family member gets a transaction in the queue on their device.
Will the original_transaction_id be the same for each user or will each user/Apple ID get their own unique receipt and set of transactions? Or is it simply a copy of the primary user?
Post not yet marked as solved
We have implemented Sign in With Apple and have a server side daily check of tokens using the "refresh_token" grant type.https://developer.apple.com/documentation/signinwithapplerestapi/generate_and_validate_tokensFor currently valid users we get a new 200 response with the Access Token as expected. However if I visit appleid.apple.com and revoke the app in there the response is "invalid_request" with a 400 response from Apple. Is this expected and is this how we tell a token is no longer valid or should we expect a different response?
ARKit 4 offers a new feature called Location Anchors and these look great. I can see us adopting these...until I read that they would only work in a few locations around the world!
Is it not possible to add a geo anchor and for my device to be anywhere? In a field for example and for me to add the 4 corners, 100ft above me for example and it to track those?
Post not yet marked as solved
Hello,As per https://developer.apple.com/news/?id=11222019a I see that the unified receipt (unified_receipt) is now live which is great. Been looking forward to that!However we are not seeing them in the sandbox at all, are they live there yet? I am still seeing old style receipt being posted to us.Thanks!Lee
Post not yet marked as solved
We have an issue where an "Archive" build of our app built with 11.2 or 11.2.1 crashes on launch.With an Xcode 11.1 Archive the app is fine. This does not affect Debug builds of the application attached to Xcode directly either.The following is what shows up as the offending code.Thread 30 name:
Thread 30 Crashed:
0 libsystem_kernel.dylib 0x0000000183476efc __pthread_kill + 8
1 libsystem_pthread.dylib 0x0000000183396d10 pthread_kill + 196 (pthread.c:1456)
2 libsystem_c.dylib 0x0000000183326a74 abort + 104 (abort.c:110)
3 libswiftCore.dylib 0x0000000190f7b2a4 swift_runtime_unreachable(char const*) + 16 (Unreachable.h:30)
4 libswiftCore.dylib 0x0000000190f7ce34 swift_getWitnessTable + 2128 (Metadata.cpp:0)
5 Plane Finder Beta 0x0000000102f3ca68 closure #1 in closure #1 in AircraftManager.fetchLiveData(bounds:) + 212 (:0)
6 Plane Finder Beta 0x0000000102f1098c thunk for @escaping @callee_guaranteed () -> () + 28 (:0)
7 libdispatch.dylib 0x0000000183330b7c _dispatch_call_block_and_release + 32 (init.c:1408)
8 libdispatch.dylib 0x0000000183331fd8 _dispatch_client_callout + 20 (object.m:495)
9 libdispatch.dylib 0x0000000183334414 _dispatch_queue_override_invoke + 672 (inline_internal.h:2484)
10 libdispatch.dylib 0x0000000183340bd4 _dispatch_root_queue_drain + 348 (inline_internal.h:2525)
11 libdispatch.dylib 0x0000000183341384 _dispatch_worker_thread2 + 120 (queue.c:6628)
12 libsystem_pthread.dylib 0x0000000183397a54 _pthread_wqthread + 216 (pthread.c:2336)
13 libsystem_pthread.dylib 0x000000018339dc7c start_wqthread + 8FB7432222 has been raised with the full crash log.
Post not yet marked as solved
I know this is more a beta question but we are seeing issues with Metal in iOS 13.1 and wanted to know if Apple know about this as for us it's a show stopper.I have filed a Radar already: FB7153939If you fire up https://developer.apple.com/documentation/metal/using_a_render_pipeline_to_render_primitives?language=objc and launch it on an iPad running iOS 13.1 the triangle is not an equilaterla triangle as it is on other platforms.It appears that the following is called twice../// Called whenever view changes orientation or is resized
- (void)mtkView:(nonnull MTKView *)view drawableSizeWillChange:(CGSize)size {
NSLog(@"%f %f", size.width, size.height);
// Save the size of the drawable to pass to the vertex shader.
_viewportSize.x = size.width;
_viewportSize.y = size.height;
}2019-08-29 15:48:29.948467+0100 HelloTriangle[2384:511317] 1668.000000 2388.000000
2019-08-29 15:48:29.968563+0100 HelloTriangle[2384:511317] 3419.000000 1165.000000Notice how the height and width on the second call are really wide and not that high! This produces a skewed triangle.
lesmond.