iPhone15 Pro 18.4beta2版本,隔空投送碰一碰:两设备靠近共享名片功能失效
Overview
Post
Replies
Boosts
Views
Activity
After updating to ios18.4, 3d scanning function, including AR function in apple clips, cannot be used. Does anyone else have the same problem?
I have a Mac Mini (M4) running macOS Sequoia 15.3.1.
I very recently downloaded and installed the current version of XCode from the app store. I have not added any extensions - it's a vanilla, un-customized, un-enhanced installation.
I have two user profiles (accounts) on my Mac: one Administrator and one Standard, each using a different apple account. I am using the Standard user account to learn XCode.
When I attempt to set up a project, I get an error message when Xcode initially tries to save the (provided) project template file. The error states:
"Failed to save Project2.xcodeproj. The backing file has been modified outside of XCode."
I am using a NAS drive to store my project file. I have also tried saving it to the Desktop. It makes no difference to the error wherever the file is being saved.
Similarly, I tried changing the Standard user account to an Administrator account to see if it was a privileges problem. Again, it made no difference to the error message. (So I changed the account back to a Standard user).
I have tried googling the error but I only find references to problems related to extension/add-in products to XCode: none of which have I added to my XCode installation.
I am attaching screenshots of the steps through the project creation process. Hopefully someone can tell me what I am doing wrong or what the problem is.
Thank you.
After the user initiates the subscription payment, the SDK returns an error type: user cancels. When the user initiates the payment again, Apple will deduct the payment twice and successfully deduct the previously cancelled SKU. This is a recent occurrence with a large amount of data, and the app has not been upgraded in any way. We need to seek help. Thank you
In my app, I have a ShareLink that attempts to share a movie.
struct MovieTransferable: Transferable {
let url: URL
let writeMovie: (URL) -> ()
static var transferRepresentation: some TransferRepresentation {
DataRepresentation(
exportedContentType: .movie,
exporting: {
(movie) in
// Write the movie into documents.
movie.writeMovie(movie.url)
return try! Data(contentsOf: movie.url)
})
FileRepresentation(
exportedContentType: .movie,
exporting: {
(movie) in
// Write the movie into documents.
movie.writeMovie(movie.url)
return SentTransferredFile(movie.url)
})
}
}
The ShareLink works if you try to share the movie with the Photos app, Air Drop, and iMessage. If I share to WhatsApp, the movie shows up as empty (zero length), but there's a movie. If I share to Discord, the movie is not displayed at all (only the comment). Instagram posts a dialog saying it won't allow movies and to use the app (why are they even in the ShareLink option for movies?). YouTube processes for a bit and then does nothing (no upload).
Are there things that I can do to make the Transferable accepted at more of the end points? It's at fps 30 and I've tried most of the available codec's. The size is the same as the iPhone's screen, so the aspect ratio is a bit odd. However, if I go directly to the app (Discord, etc...) upload from my phone works fine.
Any help would be appreciated to make this more viable.
It's 2025, and I see that trends in video storage and streaming have changed significantly. Nowadays, CDN combined with domain-based video protection is the most popular solution.
Does anyone have more insights into this technology or real-world experience with it?
I am trying to install macOS Big Sur on my VM. It gets stuck on “About 14 minutes remaining ”Does anyone know how to get past it?
I made my first payment on 27 Feb 2025,
but it was not activated after 48 hours
I contacted developer support and they said they would cancel the registration and asked me to resubmit and try again
03 Mar 2025 I resubmitted the enrollment application
05 Mar 2025 I received the enrollment request has been accepted
Then I successfully paid by credit card, but it still shows Your purchase may take up to 48 hours to process.
06 Mar 2025: The chargeback shows it's been canceled
I re-paid today. New Order Number: W1305861066
Enrollment ID: 7Z3FUQR4WV
Request help to activate my developer
Thank you
I made my first payment on 27 Feb 2025, but it was not activated after 48 hours
I contacted developer support and they said they would cancel the registration and asked me to resubmit and try again
03 Mar 2025 I resubmitted the enrollment application
05 Mar 2025 I received the enrollment request has been accepted
Then I successfully paid by credit card, but it still shows
Your purchase may take up to 48 hours to process.
06 Mar 2025:
The chargeback shows it's been canceled
I re-paid today.
New Order Number: W1305861066
Enrollment ID: 7Z3FUQR4WV
Request help to activate my developer😭
Thank you
WKWebView cannot load and display HTTP image resources
Xcode 16 iOS18 WKWebView里包含http图片时无法显示
I'm trying to use FormatStyle from Foundation to format numbers when printing a vector structure. See code below.
import Foundation
struct Vector<T> {
var values: [T]
subscript(item: Int) -> T {
get { values[item] }
set { values[item] = newValue }
}
}
extension Vector: CustomStringConvertible {
var description: String {
var desc = "( "
desc += values.map { "\($0)" }.joined(separator: " ")
desc += " )"
return desc
}
}
extension Vector {
func formatted<F: FormatStyle>(_ style: F) -> String where F.FormatInput == T, F.FormatOutput == String {
var desc = "( "
desc += values.map { style.format($0) }.joined(separator: " ")
desc += " )"
return desc
}
}
In the example below, the vector contains a mix of integer and float literals. The result is a vector with a type of Vector<Double>. Since the values of the vector are inferred as Double then I expect the print output to display as decimal numbers. However, the .number formatted output seems to ignore the vector type and print the values as a mix of integers and decimals. This is fixed by explicitly providing a format style with a fraction length. So why is the .formatted(.number) method ignoring the vector type T which is Double in this example?
let vec = Vector(values: [-2, 5.5, 100, 19, 4, 8.37])
print(vec)
print(vec.formatted(.number))
print(vec.formatted(.number.precision(.fractionLength(1...))))
( -2.0 5.5 100.0 19.0 4.0 8.37 ) // correct output that uses all Double types
( -2 5.5 100 19 4 8.37 ) // wrong output that uses Int and Double types
( -2.0 5.5 100.0 19.0 4.0 8.37 ) // correct output that uses all Double types
Hi,
I have developed an app which has two in-app purchase subscriptions. During the test, the app can successfully get the status of the subscriptions. After it's released, I downloaded it from app store and subscribed it with my apple account. I found that in most cases, the app can identify that I have subscribed it and I can use its all functions. But yesterday, when I launched it again, it showed the warning that I haven't subscribed it. I checked my subscription in my account and the subscription status hasn't been changed, that is, I have subscribed it. And after one hour, I launched it again. This time the app identified that I have subscribed it. Why? The following is the code about listening to the subscription status. Is there any wrong about it?
HomeView()
.onAppear(){
Task {
await getSubscriptionStatus()
}
}
func getSubscriptionStatus() async {
var storeProducts = [Product]()
do {
let productIds = ["6740017137","6740017138"]
storeProducts = try await Product.products(for: productIds)
} catch {
print("Failed product request: \(error)")
}
guard let subscription1 = storeProducts.first?.subscription else {
// Not a subscription
return
}
do {
let statuses = try await subscription1.status
for status in statuses {
let info = try checkVerified(status.renewalInfo)
switch status.state {
case .subscribed:
if info.willAutoRenew {
purchaseStatus1 = true
debugPrint("getSubscriptionStatus user subscription is active.")
} else {
purchaseStatus1 = false
debugPrint("getSubscriptionStatus user subscription is expiring.")
}
case .inBillingRetryPeriod:
debugPrint("getSubscriptionStatus user subscription is in billing retry period.")
purchaseStatus1 = false
case .inGracePeriod:
debugPrint("getSubscriptionStatus user subscription is in grace period.")
purchaseStatus1 = false
case .expired:
debugPrint("getSubscriptionStatus user subscription is expired.")
purchaseStatus1 = false
case .revoked:
debugPrint("getSubscriptionStatus user subscription was revoked.")
purchaseStatus1 = false
default:
fatalError("getSubscriptionStatus WARNING STATE NOT CONSIDERED.")
}
}
} catch {
// do nothing
}
guard let subscription2 = storeProducts.last?.subscription else {
// Not a subscription
return
}
do {
let statuses = try await subscription2.status
for status in statuses {
let info = try checkVerified(status.renewalInfo)
switch status.state {
case .subscribed:
if info.willAutoRenew {
purchaseStatus2 = true
debugPrint("getSubscriptionStatus user subscription is active.")
} else {
purchaseStatus2 = false
debugPrint("getSubscriptionStatus user subscription is expiring.")
}
case .inBillingRetryPeriod:
debugPrint("getSubscriptionStatus user subscription is in billing retry period.")
purchaseStatus2 = false
case .inGracePeriod:
debugPrint("getSubscriptionStatus user subscription is in grace period.")
purchaseStatus2 = false
case .expired:
debugPrint("getSubscriptionStatus user subscription is expired.")
purchaseStatus2 = false
case .revoked:
debugPrint("getSubscriptionStatus user subscription was revoked.")
purchaseStatus2 = false
default:
fatalError("getSubscriptionStatus WARNING STATE NOT CONSIDERED.")
}
}
} catch {
// do nothing
}
if purchaseStatus1 == true || purchaseStatus2 == true {
purchaseStatus = true
} else if purchaseStatus1 == false && purchaseStatus2 == false {
purchaseStatus = false
}
return
}
CFNetwork None CFURLResponseGetRecommendedCachePolicy None 0
CFNetwork None CFHTTPCookieStorageUnscheduleFromRunLoop None 0
CFNetwork None /_/_CFNetworkAgentMessageProcessorMain None 0
CFNetwork None CFURLDownloadCancel None 0
CFNetwork None CFURLDownloadCancel None 0
libdispatch.dylib None /_dispatch/_block/_async/_invoke2 None
We've observed intermittent crashes in our production environment, exclusively affecting customers running macOS 10.15 and 11. The crash logs consistently show a stack trace involving CFHTTPCookieStorageUnscheduleFromRunLoop and CFURLDownloadCancel within the CFNetwork framework. This suggests potential issues with cookie storage management and/or URL download cancellation.
Could the team please analyze these crash logs and provide insights into:
The root cause of the crashes.
Potential race conditions or synchronization issues.
Recommendations for mitigating or resolving the problem.
Your assistance in resolving this issue is greatly appreciated."
Xcode 16.2 (and also Apple Configurator) randomly stopped working since today morning.
Upon opening, the application crashes -> "unexpectedly quit".
I've tried restarting the Mac, I reinstalled Xcode, still the same issue.
This issue is currently on my MacBook Pro M4 on macOS Sequoia 15.3.1.
Problem Reporter shows:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: Xcode [5577]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 16.2 (23507)
Build Info: IDEApplication-23507000000000000~2 (16C5032a)
App Item ID: 497799835
App External ID: 870964517
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2025-03-07 00:27:05.7449 +0100
OS Version: macOS 15.3.1 (24D70)
Report Version: 12
Anonymous UUID: ---------
Time Awake Since Boot: 10000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: Xcode [5577]
Application Specific Information:
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x1975ff720 __pthread_kill + 8
1 libsystem_pthread.dylib 0x197637f70 pthread_kill + 288
2 libsystem_c.dylib 0x197544908 abort + 128
3 Xcode 0x1009af550 main.cold.1 + 28
4 Xcode 0x1009af374 main + 448
5 dyld 0x1972b8274 start + 2840
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000
x4: 0x0000000000000000 x5: 0x0000600000841120 x6: 0x000000000000000a x7: 0x0000000000000001
x8: 0x61ac7d1cc0e801aa x9: 0x61ac7d1ec01289ea x10: 0x0000000000000005 x11: 0x0000000000000005
x12: 0x000060000244c050 x13: 0x0000000000000000 x14: 0x000000019789a81d x15: 0x0000000200fc05b0
x16: 0x0000000000000148 x17: 0x00000002095ea2c0 x18: 0x0000000000000000 x19: 0x0000000000000006
x20: 0x0000000000000103 x21: 0x0000000200fa8920 x22: 0x0000000200fafd38 x23: 0x000000012b004230
x24: 0x00000001972b2000 x25: 0x0000000000000000 x26: 0x0000000000000000 x27: 0x0000000000000000
x28: 0x0000000000000000 fp: 0x000000016f453870 lr: 0x0000000197637f70
sp: 0x000000016f453850 pc: 0x00000001975ff720 cpsr: 0x40000000
far: 0x0000000000000000 esr: 0x56000080 Address size fault
Binary Images:
0x1009ac000 - 0x1009affff com.apple.dt.Xcode (16.2) <81ab48b8-11be-3fa2-9be2-a5d6494288a5> /Applications/Xcode.app/Contents/MacOS/Xcode
0x1975f6000 - 0x197630ff7 libsystem_kernel.dylib (*) <eee9d0d3-dffc-37cb-9ced-b27cd0286d8c> /usr/lib/system/libsystem_kernel.dylib
0x197631000 - 0x19763dfff libsystem_pthread.dylib (*) <642faf7a-874e-37e6-8aba-2b0cc09a3025> /usr/lib/system/libsystem_pthread.dylib
0x1974cb000 - 0x19754cffb libsystem_c.dylib (*) <92699527-645f-3d8d-aed8-1cfb0c034e15> /usr/lib/system/libsystem_c.dylib
0x1972b2000 - 0x197333f3f dyld (*) <398a133c-9bcb-317f-a064-a40d3cea3c0f> /usr/lib/dyld
0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???
0x1976a3000 - 0x197b97fff com.apple.CoreFoundation (6.9) <190e6a36-fcaa-3ea3-94bb-7009c44653da> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=884.0M resident=0K(0%) swapped_out_or_unallocated=884.0M(100%)
Writable regions: Total=804.5M written=320K(0%) resident=320K(0%) swapped_out=0K(0%) unallocated=804.1M(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Kernel Alloc Once 32K 1
MALLOC 796.2M 18
MALLOC guard page 96K 6
STACK GUARD 56.0M 1
Stack 8176K 1
__AUTH 1098K 205
__AUTH_CONST 18.3M 351
__DATA 4587K 332
__DATA_CONST 13.1M 354
__DATA_DIRTY 692K 110
__FONT_DATA 2352 1
__LINKEDIT 606.2M 2
__OBJC_RW 2374K 1
__TEXT 277.8M 368
__TPRO_CONST 272K 2
page table in kernel 320K 1
shared memory 32K 1
=========== ======= =======
TOTAL 1.7G 1755
Hi everyone,
I built a new app and pushed it to the Testflight but call/sms is not working. Doesn't Testflight support call/sms feature?
Since around March 4, 2025 off and on, we've been receiving 500 errors back from the validate_device_token endpoint on development and production. Today (March 6) we are constantly getting 500 error back.
https://api.development.devicecheck.apple.com/v1/validate_device_token
This was working previously before then. No change has happened on our end since then.
This is a critical piece for our infrastructure.
Thanks in advance.
-Matt
Having trouble decrypting a string using an encryption key and an IV.
var key: String
var iv: String
func decryptData(_ encryptedText: String) -> String?
{
if let textData = Data(base64Encoded: iv + encryptedText) {
do {
let sealedBox = try AES.GCM.SealedBox(combined: textData)
let key = SymmetricKey(data: key.data(using: .utf8)!)
let decryptedData = try AES.GCM.open(sealedBox, using: key)
return String(data: decryptedData, encoding: .utf8)
} catch {
print("Decryption failed: \(error)")
return nil
}
}
return nil
}
Proper coding choices aside (I'm just trying anything at this point,) the main problem is opening the SealedBox. If I go to an online decryption site, I can paste in my encrypted text, the encryption key, and the IV as plain text and I can encrypt and decrypt just fine.
But I can't seem to get the right combo in my Swift code. I don't have a "tag" even though I'm using the combined option. How can I make this work when all I will be receiving is the encrypted text, the encryption key, and the IV. (the encryption key is 256 bits)
Try an AES site with a key of 32 digits and an IV of 16 digits and text of your choice. Use the encrypted version of the text and then the key and IV in my code and you'll see the problem. I can make the SealedBox but I can't open it to get the decrypted data. So I'm not combining the right things the right way. Anyone notice the problem?
Context
We are experiencing inconsistent behaviour with "Sign in with Apple" across different environments (we have an app for "A" and "B" regions) on our web client in browsers.
Specifically, we have observed two key issues:
Missing email and email_verified Claims in ID Token
In some cases, the ID token received after successful authentication does not contain the email and email_verified claims.
Here the docs state that "Alternatively, if the managed Apple ID is in Apple School Manager, the email claim may be empty. Students, for example, often don’t have an email that the school issues.", but this was experienced with a non-student Apple ID.
This issue was observed for certain users in the "A" environment, while the same users had no issues in the "B" environment.
For one affected user, removing and re-enabling the "Sign in with Apple" integration resolved the issue (https://account.apple.com/account/manage/section/security).
However, for another user, the integration could not be removed, preventing this workaround (button was active, but did nothing).
In contrast, for some users, authentication works correctly in both environments without missing claims.
Inconsistent Display of App Icon and App Name
The app icon and app name do not always appear on the Apple login interface.
One user observed that the app icon and name were displayed in "A" but not in "B".
Another user had the opposite experience, with the app icon and name appearing in "B" but not in "A".
A third user did not see the app icon or name in either environment.
Questions
Why does the app icon and name not always appear on the "Sign in with Apple" login screen?
How is it possible that the ID token sometimes lacks email and email_verified claims when using the same Apple ID in different environments?
Over the past two weeks, we have noticed widespread degraded performance in iOS devices not recognizing when links are App Clips. When scanning the QR code, it identifies it as a link, not an App Clip link and tries to open the link via Safari. Once in Safari, it still prompts the user to download the full app and not open the App Clip. Scanning with the Control Center "Scan Code" button gives an indication that it understands it's an App Clip link, but still does not open it correctly. In some cases, it will say "App Clip Unavailable" which is simply not true.
After a few scans of the same QR code, the iOS device will correct itself and open the correct App Clip. There is no consistency and/or reason why it would do this.
We have had a massive influx of users complaining that it's not opening the App Clip correctly. We have not changed anything on our website or app that would alter the efficacy of this issue. Have tested on a variety of different iOS devices on a variety of different operating systems (iPads, iPhones, iOS 16, iOS 18, etc) and they all have started behaving this same way. In addition, we've tested on other apps with App Clips and they are experiencing the same issue. My guess is that there is something happening on Apple's side with apple-app-site-association issues.
We reported via Feedback Assistant but have yet to hear from anyone from Apple to acknowledge this is a widespread issue.