Beta is the prerelease version of software or hardware.

Posts under Beta tag

200 Posts
Sort by:

Post

Replies

Boosts

Views

Activity

Embedded binary is not signed with the same certificate as the parent app. Verify the embedded binary target's code sign settings match the parent app's.
My Parent app IS signed correctly. I have verified in every screen. Has anyone seen this?Thanks!XCode 10.0 beta 6---------------error: Embedded binary is not signed with the same certificate as the parent app. Verify the embedded binary target's code sign settings match the parent app's. Embedded Binary Signing Certificate: Software Signing Parent App Signing Certificate: - (Ad Hoc Code Signed)
8
0
19k
Oct ’23
Watch app doesn't receive location updates on watchOS 10 beta
Since the iOS 17 beta 6 update, my SwiftUI-based watch app, which serves as a companion to the phone app, no longer receives any location updates. Even though the permissions are set to 'When In Use' on the phone, the CLLocation delegate returns the following error every time the app requests a location update: Error Domain=kCLErrorDomain Code=1 "(null)" - The operation couldn’t be completed. (kCLErrorDomain error 1.) Additionally, the SwiftUI map does not display the user's location, indicating that the issue is not related to my CLLocationManager implementation on the watch. While debugging on the watch, I observed that the service acknowledges the permissions as granted. On the phone, my location is displayed accurately. On watchOS 9.6, the same watch app receives location updates as expected. Furthermore, other apps on the watch receive location updates accurately, even on watchOS 10 beta. This issue is not isolated to my device; my colleagues have experienced the same problem with the TestFlight build. I suspect that there may be an issue with my project configuration, although I am unsure why this was not a problem before the watchOS 10 beta. Currently, I am attempting to resolve the issue using: Xcode 15.0 beta 8 (15A5229m) watchOS 10 21R5349b iOS 17 21A5326a It is important to note that the issue is also present in watchOS 10 21R5355a.
28
9
4.5k
Oct ’23
NWTXTRecord dictionary keys are lowercased in iOS 17 beta
NWTXTRecord dictionary keys are lowercased in iOS 17, on iOS Simulator and the device. Records returned by NWBrowser in the listener block: browser.browseResultsChangedHandler = { result, changes in metadata : ["dvty": “AppName”, "txtvers": "1", "dbid": "50BFB79F"] But the actual keys are: "DvTy", "DbId". So, in iOS 17 all keys were lowercased, but not in any previous versions. And if in the app we were looking for “DvTy” key, nil is returned. The existing app simply stopped working properly in the first iOS 17 betas. Is it a bug or the app should be updated now to check for lowercased keys always? FB12309561
5
1
988
Oct ’23
Xcode beta 15.0 beta 2 cannot connect to iPhone SE running iOS 17.0 beta
macOS Version 13.4.1 (Build 22F82) Xcode 15.0 (22181.22) (Build 15A5161b) iPhone SE running iOS 17.0 beta I have a test device (iPhone SE) with iOS 17 beta installed. I am using a cable to connect it to my MacBook. Within Xcode beta, I am using the "Devices and Simulators" dialog. Attempting to "connect" the device fails repeatedly with the following message: The developer disk image could not be mounted on this device. Domain: com.apple.dt.CoreDeviceError Code: 12040 Failure Reason: Error mounting image: 0xe8000106 (kAMDMobileImageMounterCredentialsFailed: AppleConnect authentication failed or was cancelled.) User Info: { DDIPath = "/Users/***/Library/Developer/DeveloperDiskImages/iOS_DDI.dmg"; DVTErrorCreationDateKey = "2023-06-23 17:08:18 +0000"; "com.apple.dt.DVTCoreDevice.operationName" = enablePersonalizedDDI; } -- Error mounting image: 0xe8000106 (kAMDMobileImageMounterCredentialsFailed: AppleConnect authentication failed or was cancelled.) Domain: com.apple.mobiledevice Code: -402652922 User Info: { FunctionName = AMDeviceRemoteMountPersonalizedBundle; LineNumber = 2108; } -- AMAuthInstallRequestSendSync failed: 22 (kAMAuthInstallErrorAppleConnectAuthFailed) Domain: com.apple.mobiledevice Code: -402652922 User Info: { FunctionName = "-[PersonalizedImage mountImage:]"; LineNumber = 2005; } -- I also see the following error from the phone's console: Sending response: { DetailedError = "Error Domain=com.apple.MobileStorage.ErrorDomain Code=-2 \"Failed to copy personalization manifest.\" UserInfo={NSLocalizedDescription=Failed to copy personalization manifest., NSUnderlyingError=0x7a6a07b80 {Error Domain=com.apple.MobileStorage.ErrorDomain Code=-2 \"Failed to retrieve personalization manifest: Error Domain=com.apple.MobileStorage.ErrorDomain Code=-2 \"Failed to find a cached manifest (im4m) for variant DeveloperDiskImage (personalization required).\" UserInfo={NSLocalizedDescription=Failed to find a cached manifest (im4m) for variant DeveloperDiskImage (personalization required)., NSUnderlyingError=0x90ab04240 {Error Domain=com.apple.MobileStorage.ErrorDomain Code=-2 \"/private/var/run/mobile_image_mounter/DeveloperDiskImage/B5A2B06AE07F3A280BC168DCAFE0D3BADD8CFCAA017BE5C735299D5398807133F23C61593439B0B93C4B772168E8F711.im4m does not exist.\" UserInfo={NSLocalizedDescription=/private/var/run/mobile_image_mounter/DeveloperDiskImage/B5A2B06AE07F3A280BC168DCAFE0D3 I have tried the usual things: Restarting Xcode. Restarting the iPhone. Logging in/out from iCloud on the iPhone. Logging in/out of Apple Developer within Xcode. Restarting my MacBook. Burning sage and making an incantation.
8
1
4.1k
Oct ’23
iOS 17.1 Beta 2 - Bluetooth audio levels not reaching max - iPhone 15 Pro
On iOS 17.0.2 my bluetooth devices (CarPlay and earbuds) were performing at normal levels with all sound settings at default. In the gym, I like to max out my bluetooth earbuds. However, after updating to iOS 17.1 Beta 2 (21B5056e), my bluetooth earbuds set at max volume sounded medium. My first troubleshooting method was to check the sound settings... all setting (including accessibility) were left at the default inputs. To further troubleshoot, I tried other downloaded albums on my music library/playlists...all noticeably lower at max volume. I was thinking this might be related to my earbuds. However, when driving, I decided to play the same album in my 2021 GMC Sierra via CarPlay... I had to turn up the dash knob audio substantially higher to replicate what was considered loud (or rather "comfortably loud") in my truck. Apple tech supports only recommendation was to do a system restore and roll back to 17.0.2. Has anyone else tested music quality/sound over bluetooth before and after they updated from 17.0.2. to 17.1 Beta 1/2 ?
2
0
1.2k
Oct ’23
@State ViewModel memory leak in iOS 17 (new Observable)
Our app has an architecture based on ViewModels. Currently, we are working on migrating from the ObservableObject protocol to the Observable macro (iOS 17+). The official docs about this are available here: https://developer.apple.com/documentation/swiftui/migrating-from-the-observable-object-protocol-to-the-observable-macro Our ViewModels that were previously annotated with @StateObject now use just @State, as recommended in the official docs. Some of our screens (a screen is a SwiftUI view with a corresponding ViewModel) are presented modally. We expect that after dismissing a SwiftUI view that was presented modally, its corresponding ViewModel, which is owned by this view (via the @State modifier), will be deinitialized. However, it seems there is a memory leak, as the ViewModel is not deinitialized after a modal view is dismissed. Here's a simple code where ModalView is presented modally (through the .sheet modifier), and ModalViewModel, which is a @State of ModalView, is never deinitialized. import SwiftUI import Observation @Observable final class ModalViewModel { init() { print("Simple ViewModel Inited") } deinit { print("Simple ViewModel Deinited") // never called } } struct ModalView: View { @State var viewModel: ModalViewModel = ModalViewModel() let closeButtonClosure: () -> Void var body: some View { ZStack { Color.yellow .ignoresSafeArea() Button("Close") { closeButtonClosure() } } } } struct ContentView: View { @State var presentSheet: Bool = false var body: some View { Button("Present sheet modally") { self.presentSheet = true } .sheet(isPresented: $presentSheet) { ModalView { self.presentSheet = false } } } } #Preview { ContentView() } Is this a bug in the iOS 17 beta version or intended behavior? Is it possible to build a relationship between the View and ViewModel in a way where the ViewModel will be deinitialized after the View is dismissed? Thank you in advance for the help.
3
12
2k
Oct ’23
Major Screen Time Bug
As a parent I was so excited to hear about Screen Time, so much so that I upgraded my sons phone to iOS Beta 2 when it came out.As a parent I setup his access on my phone for his phone and set it so that he could not longer browse the web, watch YouTube etc after 10 PM at night. As before I would go in his room at night and he would be watching videos at 1 am.... (grr)Anyways Screen Time was a blessing until the other night when I heard him up at 1 am and went into his room and there he was watching videos on his phone. For some reason Screen Time wasn't shutting of his app access at 10 PM like it was supposed to.I asked my son how he was able to get around screentime and he told me... (and I consider this a big bug!)When Screen Time kicks in and shuts his apps off, he goes into Settings > General > Date & Time and then turns off "Set Automatically" and then changes the time to a time which he is not restricted by Screen Time, which then unlocks all the apps again.I thought that was smart of him to figure that out and I have not found a way to restrict him from changing his date and time settings.Last night, again he was on his phone after bed time... and I caught him. He said he found an easier way to defeat Screen Time, and he did that by setting the Time to 24 Hour Time, for some reason Screen Time does not understand 24 hour time.I hope this can be fixed by Apple, as if it can't it negates the entire reason for parents to have Screen Time.Thanks,Scott
10
2
23k
Oct ’23
NavigationPath and navigationDestination with custom back button fails on iOS 17 BETA
Using the new navigationDestination and NavigationPath functions previously on iOS 16 everything has been working fine using a custom back button, which calls path.removeLast(). However, if we try this on iOS 17 BETA 5, the screen being removed flashes white. Also, how can I raise this as a bug with Apple, so they can fix it before the release of iOS 17. You can try this code as an example (NOTE THE WHITE FLASH ON REMOVE LAST): struct DetailView: View { @Binding var path: NavigationPath var body: some View { ZStack { Color.black VStack(alignment: .center) { Spacer() Button(action: { path.removeLast() }, label: { Text("BACK") }) Spacer() } } } } struct ParentView: View { @State var path: NavigationPath = .init() var body: some View { NavigationStack(path: $path) { ZStack { Color.red VStack(alignment: .center) { Spacer() Button(action: { path.append("TEST") }, label: { Text("FORWARD") }) Spacer() } } .navigationDestination(for: String.self) { _ in DetailView(path: $path) } } } }
5
1
903
Oct ’23
Firebase and Compiling errors with Xcode 15.0 beta 2
I am getting the following errors when I attempt to build my project since I updated Xcode to Version 15.0 beta 2 (15A5161b). I am wondering if anyone could help me figure it out as I have already cleared the cache and the build folder as well as reinstalling the firebase package entirely. Here are the two errors I have been receiving: "failed to verify module interface of 'Project_Name' due to the errors above; the textual interface may be broken by project issues or a compiler bug" (The code on the line this error is on is on a autogenerated file titled "Project_Title.private" and cannot be edited, "// swift-interface-format-version: 1.0") The other error I assume also has to do with the above issue, "no such module as 'firebase'" ( the code on line of question is "import Firebase".) I would appreciate ay help I could get because I cannot find any documentation or similar problems. I have attached screenshots below for your convenience. Thank you for your help!
5
2
1.4k
Oct ’23
Apple ID username or password is "incorrect" while trying to install OS X 10.11
After trying to install OS X El Capitan onto my hard drive, I've come across a problem. When it asks me to sign into my Apple ID I do with the correct information. It then says that my username or password is incorrect. I know this is not the case because I have reset my password and tested it by signing into the App Store on my phone. Anyone else have this problem? Any fixes? Thanks.
39
0
58k
Oct ’23
iOS Spotlight indexing seems to be broken on iOS 17?
Content indexed through CSSearchableIndex.default().indexSearchableItems() is no longer searchable from Spotlight. I created a very small app to demonstrate this. CSSearchableIndex.default().indexSearchableItems() returned no error, yet the result can't be found. import CoreSpotlight import SwiftUI @main struct testspotlightApp: App { var body: some Scene { WindowGroup { ContentView() .onContinueUserActivity(CSSearchableItemActionType, perform: handleSpotlight) } } func handleSpotlight(_ userActivity: NSUserActivity) { print("Found \(userActivity.userInfo?.debugDescription ?? "nothing")") } } import CoreSpotlight import SwiftUI struct ContentView: View { @State var result = "" var body: some View { VStack { Text("Hello!") Button { let attribute = CSSearchableItemAttributeSet(contentType: .text) attribute.title = "a page title" attribute.contentDescription = "hello this is a page" attribute.keywords = ["search", "this", "page", "title"] let item = CSSearchableItem( uniqueIdentifier: "12345", domainIdentifier: "com.test", attributeSet: attribute) CSSearchableIndex.default().indexSearchableItems([item]) { error in if let error { result = "Failed to index: \(error.localizedDescription)" } else { result = "Successefully indexed to spotlight. Try searching 'a page title'" } } } label: { Text("Index a page").font(.title) } Text(result).multilineTextAlignment(.center) } .padding() } } Has anyone else seen the same issue?
15
9
3.8k
Oct ’23
iPadOS 17 "Could not locate device support files"
On XCode 14.3.1, downloading support files for iPadOS 17, fails with message: **Could not locate device support files You may be able to resolve the issue by installing the latest version of Xcode from the Mac App Store or developer.apple.com. [missing string: 869a8e318f07f3e2f42e11d435502286094f76de]** on XCode 15.0 beta (15A5160n), iPad does not show up. Have rebooted Mac, iPad, Settings > Clear Trusted Computers => no iPad in XCode 15 => missing support files message on XCode 14.3.1 Am stuck. How to get unstuck quickly?
8
3
23k
Oct ’23
Dirty shutdown "shutdown -u"
Hi, For some reason, dirty shutdown is no longer working for me under 10.12 betaI have a script running that switches of my Mac Pro 5,1 at midnight every day. Since I travel a lot, I can remotely switch on my Mac Pro with an remotely controlled power plug switch off/switch on. Works like charm - until now. Looks like something has changed with 10.12... Anybody has an idea? Is it still working for you?Steps to reproduce:1) shutdown via terminal "shutdown -u now"2) wait until shutdown and a few minutes3) unplug the power plug and replug. Computer should start.Please note: if you do a regular shutdown, and then unplug and re-plug, computer will not start.
2
0
990
Oct ’23
iMessage has merged 2 conversations of 2 different contacts
Hi all,I've 2 separate conversations with 2 different contacts (not the same phone number, nothing in commun).On my MacBook (High Sierra) everything works fine.But on my iPhone X running iOS 12 beta 3 (since beta 2 I've this bug), these 2 conversations are merged.When I write to one or another of these 2 contacts, it displays the 2 conversations in one screen. It merges them.When I try to create a new message, when I enter one of the 2 contacts, I don't know who receive the message, it's not always the same one that receive the message.That's really annoying.Does anyone have this issue too?I filled a bug reporter for that.Regards,Alexandre
21
2
41k
Oct ’23