Same problem here, really frustrating because my update has some fixes for potentially crtiical bugs. I did not change anything in regards to signing or the profiles.I also tried (after it has been rejected for the first time) to create new profiles. Unfortunately it did not solve the issue.Yesterday my app passed the initial check and I could select the build. But after submitting it for review, it was rejected manually for the same reason.
Post
Replies
Boosts
Views
Activity
After five rejected builds, I deleted everything. I created new provisioning profiles etc, cleared all caches and rebuilt the app.It looks like App Store Connect is happy now.
I have the exact same problem.
On the Watch side, everything seems to work just fine and
session( session: WCSession, didFinish fileTransfer: WCSessionFileTransfer, error: Error?)
will be called (with no error).
But on the iPhone side
session( session: WCSession, didReceive file: WCSessionFile)
just won't be called.
I am pretty much using the same code as above, but I am trying to update my widget once every 3 seconds. But there seems to be minimum period of at least 5 minutes? The simulator always shows that the next refresh is in 5 minutes.
This is my code:
func getTimeline(in context: Context, completion: @escaping (Timeline<WidgetModel>) -> Void)
{
let controller = BatteryController()
controller.refresh()
let nextRefresh = Calendar.current.date(byAdding: .second, value: 3, to: Date.current)!
		let model = WidgetModel(date: nextRefresh, batteries: controller.batteries)
		let timeline = Timeline(entries: [model], policy: .atEnd)
		completion(timeline)
}
Is this true that the minimum refresh interval is 5 minutes?
Thank you for your answer.
Just out of curiosity: Apple refuses to revoke old certificates. Can you maybe tell me why? I am absolutely sure that the first two certificates that I had created are not being used.
I can absolutely understand that certificates are not something that are handed out without any hesitation (or maybe not at all), but in my case a simple workaround would be to simply revoke one or two certificates so I can create a new one.
Regards,
Sascha
Just an update if anyone ever runs into the same problem:
I am still waiting for an answer to my support ticket that I created almost 4 months ago...
I do not want to create another developer account, because I do not know if this is ok to own more than one developer account as an individual. But I really don't know what else to do, because I can't (and don't want to) wait any longer.
I messed this up, so I don't (and can't) want to blame Apple for this. But it seems like a pretty straightforward yes/no answer. Either grant the exception or don't. But at least let me know...
I never even received any email from DHL or anything like that. I think March 8th was the first deadline and now I don't know what to do? Any advice?
I have repeated the test in a command line tool and the results are the same.
Thank you for your reply!
So if I understand this correctly, the proper way to handle this problem would be the following:
The main application contains a page where the user can add paths to observe. The user would select the path using a NSOpenPanel.
The path will be stored as a secure bookmark.
All paths that are stored as secure bookmarks can now be used by the extension.
I have one question though: You mentioned that simply using "/" is bad if other extensions do the same thing. Let's assume the user selects "/" because all directories should be used by the Finder extension.
What if the user now installs another extension that does the same thing? What does "ned badly" mean in this case?
Regards,
Sascha
Hello,
thanks for the reply, now I understood what you meant. I thought that there was some technical problem. But of course it can get wild, if two extensions try to update the badge icons for the same files / folders.
What is the best way to transfer the data of the scoped URL to the Finder Sync extension? I have tried to use a distributed notification, at least the message is sent and delivered to the extension. All I can pass is a string though.
Regards
I found a solution: create a new macOS version for this app and then hover over the iOS build - a delete button appears.
I created a new app that creates a new CBCentralManager instance and sets the delegate. The delegate functions are called properly, so this issue seems to be related to my app specifically.
Other BLE scanner apps also seem to work fine. I tried deleting some Bluetooth Caches, but that did not solve the problem.
When using the same basic code from the example app in my production app, no delegate functions are called. Very weird. Monterey will be released tomorrow, so I am quite under pressure here 😢
The scanning process starts after the state has changed to poweredOn.
I then get this error:
Invalidating assertion 236-151-4668 (target:[app<application.appid.125946431.126032515.61252494-CF92-4555-8108-9155B47AA89C(501)>:1869]) from originator [daemon<com.apple.WindowServer(88)>:151]
Closed XPC connection to session "appid-central-1869-41"
Unregistering session "appid-central-1869-41"
This pretty much appears as soon as I start the app. Bluetooth entitlement is set in the entitlements file.
Every single Bluetooth device works fine on my iMac and yet I think that there is something really wrong regarding Bluetooth.
Because of all this trouble I completely reinstalled macOS Monterey (I even wiped the hard drive). After reinstalling macOS Monterey, I encountered the exact same behaviour.
I have read online, that you can (in theory) reset your Bluetooth adapter by pressing Command and Shift (or only Command) and the clicking the Bluetooth menu in the menu bar.
There is additional information, but no option to reset the Bluetooth adapter.
Another problem is that there is no com.apple.bluetooth.plist file in the Preferences folder.
I really don't understand this at all.
Just half an hour ago, I had to restart my iMac because the mouse did not scroll anymore. I just thought that my mouse had died, but after restarting, everything worked fine.
I created a ticket a couple of days ago and got a reply pretty fast. It was escalated to the Bluetooth team, but I did not anything back from them.
Since a couple of days I have. weird issue with my Apple Magic Mouse 2. Sometimes the mouse cursor just jumps a rather large distance, it is very weird.