I have an older phone that I would like to use for testing. It is an iPhone 6s running iOS 11.4.1I can run my app on the device, but I can't run any unit tests. When I try, I get the following error:dyld: could not load inserted library '__PLATFORMS__/iPhoneOS.platform/Developer/usr/lib/libXCTestBundleInject.dylib' because image not foundIf I try the exact same thing on my new iPhone 11 Pro running iOS 13.2.3, I get the same error, but the tests work fine.I've only seen this problem definitively referenced one other place: github.com/CocoaPods/CocoaPods/issues/9165I tried added "-weak_framework XCTEST -weak-lXCTestSwiftSupport" to linker flags and "$(PLATFORM_DIR)/Developer/usr/lib" Library search path, but it didn't help. I tried cleaning the build folder, deletingn the previous app, and restarting the device. Same problem.I guess I should have upgraded to iOS 12 when I had the chance. I didn't expect to get blocked on something like this. I would like to have some backwards compatibility. Is there any other way to upgrade an iOS13-capable device to iOS 12? I think the iPhone 6 was one of the few that is only upgradeable to iOS 12. I might be able to find one of those. Any other suggestions?
Post not yet marked as solved
I have a free app in the Mac App Store. One day recently, I saw a strange 10x spike in "units" (free downloads) from Denmark. Sadly, there was no corresponding spike in in-app purchases. I saw a similar one-day spike last year but that seemed to come from the US. This one was entirely from Denmark. It only shows up on the "Sales and Trends" page. There is no matching spike on the app analytics page.Has anyone else seen something similar? Is this something to be concerned about? There are lots of scams and frauds on the internet. I don't want any of those people taking an interest in me.
Post not yet marked as solved
Someone please correct me if I'm mistaken, but I think Apple just deprecated the entire help infrastructure in Mojave.I am doing final testing on a new build of my app. It really bugs me that help anchors don't work. It seemed like I could sometimes get them to work in the past. But now, nothing. It is just a webview, so I decided I would just scrap the whole thing and do it all myself. 2 hours later, that's done. However, I still wanted to use those convenient anchors. I figured I would just call hiutil at runtime to extract the anchors and I would be all done. But hiutil doesn't work on Mojave anymore. It seems seems to create them OK. I can use hiutil to read a helpindex file created on Mojave. But I can't read the same helpindex file on Mojave. I suppose that's irony for you. The one piece of the old help infrastructure that I thought I could salvage in my new version is now broken.Congratulations, Apple! That's the sound of one hand clapping.
Is this possible? And if so, how does one do it?All I need is a handful of NSUserDefaults settings. No CloudKit, no documents, nothing fancy.So far, I have found the following:1) I seem to have the correct entitlement. The default value for com.apple.developer.ubiquity-kvstore-identifier is $(TeamIdentifierPrefix)$(CFBundleIdentifier). I have tried to manually set what those values are, but there is no change in behaviour.2) I don't think I can use "Automatically manage signing". It seems to pick my "Mac Developer" certificate and doesn't allow me to change that. This is a Developer ID app, so this seems like a dead end. Just for fun, I tried the automatically managed, wrong certification with no change in behaviour.3) I can seem to manually specify the correct Developer ID certificate and it picks up the provisioning profile correctly.4) Regardless of how I try the signing, the app won't run from Xcode. All I ever get is "warning: Falling back to contents of entitlements file ... because it was modified during the build process. Modifying the entitlements file during the build is unsupported." As far as I know, I'm not doing anything of the sort. It spits out this message 5 times after copying various embedded frameworks and resources. Eventually I get "Message from debugger: unable to attach" in the console.5) If I do an archive, it will run. Obviously it doesn't work. There is no iCloud functionality.6) The iCloud tab in Capabilities seems happy.7) According to the documentation, it isn't possible. 8) According to WWDC 2016 "What's new in Security", it is possible.Any ideas? Hints? Tutorials? Thanks.
Post not yet marked as solved
I just experienced a problem in my app where I could not completely make it the key window and process first responder status. I first noticed there was a problem because I click on my app's notification icon and the app did not activate. If I manually switched to it, it acted like it as an inactive window and I could not activate it. There was one window that I couldn't activate at all. This is somehow related to multiple displays. When I plugged in my external display, I was able to get it working. I have seen this same problem before in other apps. Messages in particular was doing this for a long time. But after connecting and disconnect my external display, Messages is working now too.Does anyone know the cause of this problem and how to fix it? Thanks.
john daniel.