Post not yet marked as solved
Ok, the issue turned out to be that the iOS device lost internet connection and therefore couldn't verify the signature to run the app.
Post not yet marked as solved
I found out that as of Xcode 12.2 SwiftPM do not work reliably with playground. Currently, I can't make it work.
I use 2 slightly different ways to marry a package with playgrounds: by connecting them through a workspace and through a project. It worked once, and to make it work I had to restart Xcode. But since I decided to replace the package, I was unable to make it work ever since.
At this point I'm not sure if I'm doing something wrong or is it an Xcode bug. I've decided to stop trying and give up on playgrounds until SwiftPM support will become dead simple. Too many hours wasted.
Build active scheme is turned on.
Post not yet marked as solved
Same problem here. The certificate is not missing, it is actually present in the keychain on computer. I'm using automatic signing for building the archive and for distributing it.
What makes it worse, I actually was able to upload an archive without error earlier today. But not anymore. Have this error on 2 different Macs.
Post not yet marked as solved
Same issue, August 2020.
Trying to enter password for dev account and see "session has expired" immediately in Xcode 11.6. However, if I open Xcode 12 beta 4, the account is marked as logged in.
P.S. I'm on Big Sur beta 4.
Post not yet marked as solved
Have the same problem. My account is due to expire, and my 2 payment attempts were cancelled without an attempt to charge the card. I know from different social media threads that many other Russian developers and developers from other countries suffer from the exact same issue and only support could help them by manually charging the card.
What make it worse for me is that the support leaves my requests unanswered. I have case numbers but they are useless, because there's no way for me to contact the support. (There's no phone call option on the dev support site).
This really is bad.
Post not yet marked as solved
Thank you for reaching out.I found the issue, and it had nothing to with Safari. The problem was me, misusing Combine: I wrapped calls to SFSafariExtensionManager.getStateOfSafariExtension and SFContentBlockerManager.getStateOfContentBlocker in Future<> and didn't keep AnyCancellable which was produced as the result. Thus, the result of the operation never made it to the state.Curiously, I remember the same code working before. Maybe during Beta times, there might have been a bug when a Combine chain wasn't disposed immediately. So I started looking into it thinking nothing is wrong with my code 🙂 Everything is fixed now.Thank you.
Post not yet marked as solved
I solved my issue. I haven't noticed that the placeholder details view didn't have .frame modifier allowing it to expand. So it acted as a limiter. But the real details view has .frame, so the moment the real view is activated by selection in master the NavigationView finally expands.
Scratch that, I'm just stupid. I didn't notice I already have the local repo dependency on the same package in the project. Removing it resolved the issue
Post not yet marked as solved
Yep, same here.P.S. In case if it helps someone else, as a temp workaround I switched to listening to my music through browser (musi.sh service that you can connect to Apple Music acount).
Post not yet marked as solved
In Beta 2 there's now an error saying than NavigationView is not available on macOS. Let's hope they will stick to their original WWDC session and will implement it later.
Had this issue on my MacBook Air.Was able to sign in into Mac AppStore right after I signed into Music app. My guess is that action somehow cleared stalled authentication state of AppStore.Give it a try.
