Post not yet marked as solved
For many people Xcode 12 beta 4 crashes whenever they try to open an existing project.
There do not appear to be any other problems.
Post not yet marked as solved
None. Individual transactions are never reported.It might help if you could say what exactly you are trying to achieve. The in-app purchase receipt says that a purchase has been made, so it is made, so the app should behave as if it had been made (and so should your server, if you have a server).Are you trying to check whether Apple are paying you for the in-app purchases they sell? Or what else are you trying to do?
Post not yet marked as solved
I have now distributed two apps with this warning, and they are working well with no evil consequences.
Post not yet marked as solved
What status is App Store Connect reporting for these apps? Is it "In Review", "Waiting for Review", "Ready for Developer Release", "Ready for Sale"?
Post not yet marked as solved
I had this confirmed by Apple DTS for an exactly similar crash problem: the App Store uses the buggy compiler, mangles the app so that 32-bit devices can't run it, and then goes ahead and installs it anyway.Our crash also involved OpenSSL, and the recommended cure is indeed to turn off "Include bitcode" because then the mangling doesn't happen. In fact you can reproduce the problem for yourself locally by taking a suitable build, archiving it, pressing "Distribute", taking the "Development" route, and turning ON the "Rebuild from Bitcode" option.Xcode 11.5 cures this problem locally, so the problem will be cured when the App Store publication process starts using tools from that version. When I asked, the App Store people said that the version of the tools they use was not something they are prepared to reveal, so we will never know when it is safe to turn on "Include bitcode" again.
Post not yet marked as solved
No. I have just tried (in a project with no third-party code).
FB7668750
Post not yet marked as solved
This is probably the same bug, still present in iOS 13, which has been reported to Apple as FB7538414.
Post not yet marked as solved
In my experience, this affects the 64-bit iOS 8.1 simulators only.iOS 8.3 is OK.32-bit simulators are OK (although they will probably stop working altogether in macOS 10.15).
Post not yet marked as solved
I think the trouble is that since the exchange rate is not established until the payment has actually been made, the choice would be either to delay the financial reports until the payment date – which is depriving developers of useful information – or to mutate the reports suddenly when the extra information becomes available, which means that the report you downloaded yesterday may be not the report you download today.What we do is download the detailed financial report when it becomes available, and when the payment report becomes available, listing the amount for each region in the region's currency and our home currency, we run a process on the database to infer the exchange rate and fill in "home currency" amounts for each app and subscription. It is a bore but not a huge bore, since it is only monthly and it is only one entry per region rather than per-app-and-IAP-and-region.
Post not yet marked as solved
I think it might be helpful if you explained "doesn't work". What actually happens and how does it differ from what you expect?For instance, "doesn't work" could mean "the dialogue doesn't appear" or "the dialogue does appear but makes no difference".If you do establish this as a bug then it would be reasonable to appeal against the rejection on the ground that it is only the bug in macOS which is forcing you to request the temporary exception. But it might be a case where you need to raise a DTS incident to get official confirmation that it is a bug – as well as raising a bug report, of course.
For anyone else who has this sort of problem in future, the official DTS reply is that it is impossible to get the behaviour that contacts and Pages files exhibit, whereby the icon is shown in Mail and tapping on the icon opens the relevant app. Mail is specifically programmed to handle those file types differently from others.
Thank you, Quinn, for your help so far. I can entirely see why icons and file types aren't your métier. They are fundamentally arbitrary and non-rational. At least networking questions are founded, at some level, on reason and the laws of nature.I do actually have a DTS incident in progress. As far as I can work out, the man completely misunderstands how file types are supposed to work, and it is quite hard to educate him. He thinks that "public.content" and "public.data" are declarations about my app, not about the file type, and that I should not be using them, whereas the first thing you told me was that I should be (as also does what Apple documentation I have managed to find).For what it's worth, I agree with you rather than with him, but since no setting of UTTypeConformsTo makes any real difference anyway…… anyway, you're well out of it and I will continue to enjoy reading your networking answers!
Nothing like experienced eyes!The setting of CFBundleTypeName to 'com.universalis.ripcard' sounded irrational since that made it a duplicate of LSItemContentTypes[0], but I did it anyway; and removed the ".png" suffixes too.Unfortunately none of this has made any difference. All the behaviours I described at the bottom of the post with the 'Info.plist' extracts are exactly the same, after these changes.
Post not yet marked as solved
I thought it might be worth addressing the "obviously" at the beginning of your question.Developers do not, in general, acquire every Apple device that is going. It is perfectly possible to develop software for the whole range of iPhones from 6 to XS purely by having one test device and simulating the rest.The main exceptions to this are if you are using a hardware feature that an old device doesn't have. For instance, if you seriously depended on Force Touch then you would have to have a 6s at the very least. But simple things such as the changes of screen size and layout that accompany new devices can usually be handled perfectly well in the Simulator.The only times I have deliberately delayed updates until I had the device in question were the very first iPad and the very first Apple Watch. This is because the user experience was different enough that one couldn't imagine it without actually getting one's fingers onto the device itself.As for your question about phones, I don't want to get into that because I am not an expert. But if I just buy a phone then it doesn't become my main phone unless I specifically set it up as a replacement for my old phone in iTunes and specifically move my old SIM card to my new device. I don't have to do either of these things.
