im having the same lol

I had to create virtual machine with Sonoma , install Xcode 15, then from the main machine with Sequoia but running Xcode 15, ( can be the same done in Xcode 16 this part ) create a provisioning profile, export developer profile from Xcode , export the two certificates I saw on my system keychain access regarding to apple developer. On the virtual machine (Sonoma), import the certificates exported from the keychain , add it to System ( not to login ) , in Xcode, import the developer profile, in the App general, instead of Xcode managing the provisioning profile, select to import and select the provision profile you made at developer.apple.com ( be sure to select iOS , on the devices show all and select all Macs and phones.. and everything ;) Then create the Archive, right click + show in finder. copied the xarchive to my sequoia os machine, and upload from there

I had to create virtual machine with Sonoma , install Xcode 15, then from the main machine with Sequoia but running Xcode 15, ( can be the same done in Xcode 16 this part ) create a provisioning profile, export developer profile from Xcode , export the two certificates I saw on my system keychain access regarding to apple developer. On the virtual machine (Sonoma), import the certificates exported from the keychain , add it to System ( not to login ) , in Xcode, import the developer profile, in the App general, instead of Xcode managing the provisioning profile, select to import and select the provision profile you made at developer.apple.com ( be sure to select iOS , on the devices show all and select all Macs and phones.. and everything ;) Then create the Archive, right click + show in finder. copied the xarchive to my sequoia os machine, and upload from there

I had create a virtual machine with Sonoma, also create a provisioning profile, export developer profile from Xcode in the main machine , export the two certificates I saw on my system keychain access regarding to apple developer. On the virtual machine, Xcode 15 import the certificates exported from the keychain , add it to System ( not to login ) , in Xcode, import the developer profile, in the App, instead of Xcode managing the provisioning profile, select to import and select the provision profile you made at developer.apple.com ( be sure to select iOS , on the devices show all and select all Macs and phones.. and everything ;) Then create the Archive, right click + show in finder. copied the xarchive to my sequoia os machine, and upload from there

I had to do this, also create a provisioning profile, export developer profile from Xcode , export the two certificates I saw on my system keychain access regarding to apple developer. On the virtual machine, import the certificates exported from the keychain , add it to System ( not to login ) , in Xcode, import the developer profile, in the App, instead of Xcode managing the provisioning profile, select to import and select the provision profile you made at developer.apple.com ( be sure to select iOS , on the devices show all and select all Macs and phones.. and everything ;) Then create the Archive, right click + show in finder. copied the xarchive to my sequoia os machine, and upload from there

secured @#enclave crap. im on Sequoia, running Sonoma on the virtual m , and cannot sign in to Xcode.. I need to upload my app to the appstore connect without getting a binary invalid earn

im having the same, was trying this fix here https://developer.apple.com/forums/thread/117438 by Go to Organizer Right-Click on your app archive -> show in Finder Right-Click on the .xcarchive -> Show package content Go to Products/Applications/"AppName".app/ Open the info.plist Find the BuildMachineOSBuild and change it to the latest public MacOS release (18F132 for macOS 10.14.5)

@Robertsmania come check the link and how to fix, if you need any help with this let me know

anyone want to see the code to circumvent the issue and the CustomStepper ? Click here to the StackOveflow link

Hey @eskimo just to let you know I did fix and published already to the appstore, did a conditinoal check via ProcessInfo.processinfo.isiOSAppOnMac and did throw in a custom stepper which I had to build and act as the original stepper component :D so everything is running smoothly on the Mac right now :D I just hope that gets fixed by Apple , because just imagine... that's a very very common ui component to use.. so if any iOS app that has a stepper at some point integrate it into it, it will render the app unusable on the Mac, which I know with this M chips this compatibility thing is a Huge claim by apple on its software environment , I mean.. the whole compatibility thing its a sales point already... but that little bug.. will make a bunch of apps crashing and unusable

Hey @eskimo ! Foes your buddy has insights on whats happening…? And/or if theres a way to circunvemnt …? i was thinking maybe having a conditional to detect if the app is being run on mac and if so maybe throw a custom made stepper …? But i dont think thats possible

Report on : https://qtext.io/jayr

did someone got how to fix it ???

finally someone with the same crap happening, im breaking my head today over this. have Sonoma 14.1.2 , using the stepper via macOS (designed for iPhone) is giving me the same EXEC BAD ADDR , I have a MacBook Pro m2 . today is feb 13 2024, and it crashes for me ... anyone has a fix ???

im having the same issue now , the getTimeline is being called multiple times, can't figure out what's going on. plain simple entry here: on my real calls, im calling to an api and and have a background process downloading 3 images into memory, when this happens its calling the api all those times and running the download image process all of those times, and of course it crashes at a point cuz of memory going after 30MB -- Xcode 15 -- let currentDate = Date() let updateDate = Calendar.current.date(byAdding: .hour, value: 5, to: currentDate)! print("NEW Current Date:\(currentDate) update Date is: \(updateDate)") let entry = SimpleEntry(date: Date(),configuration: ConfigurationIntent(), items: DummyData.data) let timeline = Timeline(entries: [entry], policy: .after(updateDate)) completion(timeline) -- DEBUG console , running real device -- NEW Current Date:2023-10-18 13:58:34 +0000 update Date is: 2023-10-18 18:58:34 +0000 NEW Current Date:2023-10-18 13:58:37 +0000 update Date is: 2023-10-18 18:58:37 +0000 NEW Current Date:2023-10-18 13:58:38 +0000 update Date is: 2023-10-18 18:58:38 +0000 NEW Current Date:2023-10-18 13:58:40 +0000 update Date is: 2023-10-18 18:58:40 +0000 NEW Current Date:2023-10-18 13:58:40 +0000 update Date is: 2023-10-18 18:58:40 +0000