Post not yet marked as solved
Deployment target is set to 14.0 for all parts of my app (Main app, Widget extension, Watch extension and this one as well). So I doubt it could cause this issue.
Post not yet marked as solved
The line with " if let bestAttemptContent = bestAttemptContent {" is in the template of Xcode and does not come from Google at all. That is how Xcode creates this service extension if added.
And the print yields nothing because it is never getting called. I receive the push on my device but this extension won't get called for some reason..
Post not yet marked as solved
Thanks for the reply.
The line you mentioned is from the template that Xcode generates if you create such an extension. So if this is the problem, Apple included a not working template which would be very bad.
The debugger is also never hit if I place breakpoints in it, even if they are on line one of the function.
And yes, FCM is the Firebase Cloud Messaging which seems to work (I get push notifications at least but I don't know if something prevents it from including the mutable content flag; tried "mutable-content" as from Apples documentations as well as "mutable_content" from the FCM documentation).
Post not yet marked as solved
For everyone with the same problem: Seems like it is an issue with iOS 13 and newer as described here: swiftydorado.github(dot)io/posts/2020-01-18-multipeer-connectivity/
It seems that after introducing the new SceneDelegate on iOS 13, MCAdvertiserAssistant is not working properly.
@OOPer first of all: Thanks for your detailed explanation and help. Many of the topics you pointed out are also issues in other parts of my app (and I was already wondering why it sometimes acted in a strange manner). Learning Swift is really different compared to C Sharp (why does the hash symbol starts formatting here?) and C++. Seems like it works now as expected but I got a new question based on your response. Is there a specific reason you put the Add/Remove methods from the ViewModel into an Extension to Player instead of the Player itself? Is this just to keep it seperated or does it provide any other advantage I do not notice right now?
Thanks for the reply. Seems like I only had to do two changes. One is making my Player class inherit from ObservableObject and two is switching my @State to @ObservedObject for the player. I thought that @ObservedObject is only for things like ViewModels but totally overseen the fact that in this case my Model became my ViewModel for this Control.
Seems like I still have a long way to learn how to apply Swift and SwiftUI correctly - especially the architecture part. Anyway, thanks for your reply it just fixed all errors I still had.
Post not yet marked as solved
I was not able to solve this yet... I requested help from Apple but no response even through a TSI ticket...
Thanks for the answer. Thats sad because some of Apples support stuff are telling the users that is something the developer has todo... I already had some users with such a reply from them.. Currently I ask my users to make those "claims" thorugh reportaproblem.apple.com...
Post not yet marked as solved
I'm more or less glad that I'm not the only one with the issue. But still waiting for Apple to reply on my ticket... I'm now at about 20 mails per hour from users with the issue - that's a absolute mess for a release version, why did TestFlight work and the release is not, that makes no sense at all. Also a very old app from me is still working (using the same code base) while anything updated this year is not.
Post not yet marked as solved
I don't know how Apple handles the embedded On-Demand Resources internally but maybe there is a link. But in this case, it should work now which is not the case. I opened a ticket but 2 business days is very long if you have ~100 new users per day and it is required to use the app...
Post not yet marked as solved
I never hosted this assets on my servers. I always uploaded the on-demand resources bundled with the ipa to Apple and the apps did download the asset from there. This works for the TestFlight version even now but since last night it won't work for the release version of any of my apps.
Post not yet marked as solved
Thanks for your response. Based on that, it should be enough to addNSExtensionPointVersionwith value "3.0" to the Info.plist (this key wasn't there before at all) but this didn't change anything. Do I also have to compile with XCode 11 for this to work? Because the normal iOS App Dark Theme did worked without it just by querying the UI Style.
Post not yet marked as solved
I don't think that there is a bug in the connect portal for the IBAN simply for the reason I changed my account three weeks ago and it works fine. So either your IBAN is wrong or you do something wrong. I would rather check my IBAN with a small local script instead of some website, see: https://de.wikipedia.org/wiki/Internationale_BankkontonummerAfter validating the IBAN I would go through the setup process step by step.1. Setup bank account in ITC under Agreement, Tax, and Banking / Banking2. Setup Tax Forms in ITC under Agreement, Tax, and Banking / Tax3. Setup "Pair Apps" in ITC under Agreement, Tax, and Banking / Agreement4. Setup the In-App-Purchases in your App and don't forget to submit them with your app to the review process (otherwise they work in TestFlight but not in the release - e.g. your button don't work)
For anyone with the issue: Install XCode 11 Beta (you can it install parallel to the release version), start it once and then, if it does not work, restart the mac. After that it should work to install the IPSW file through iTunes.
Restarting the mac seems to help for this kind of issues if someone facing the same one...
