I installed the project OneSignal plugin. And I realized all the directions. But when I run the application on the virtual phone as well as on the actual phone, I get a black screen problem. I get a report on xCode. Is this the cause of this?
2017-11-01 11:52:42.016918+0300 Perakende Kart[34766:1066611] ERROR: Error!
iOS Simulator does not support push! Please test on a real iOS device.
Error: Error Domain=NSCocoaErrorDomain Code=3010 "remote notifications are not supported in the simulator"
UserInfo={NSLocalizedDescription=remote notifications are not supported in the simulator}
Related
If I list all devices, I get my device:
Found 00001020-0006613KJF902E (D431AP, iPhone 11 Pro Max, iphoneos, arm64e) a.k.a. 'P’s iPhone' connected through USB.
But if I try to select it either with 00001020-0006613KJF902E or P’s iPhone,
I get the message: The platform "P’s iPhone" does not appear to have been added to this project.
Running cordova run ios --device completes with this message:
No target specified for emulator. Deploying to "iPhone-SE--2nd-generation-, 13.6" simulator.
What could I be doing wrong? I went to XCode and added the signing things as well.
When attempting to install a WatchKit app to the watch device, through Xcode 8, I'm seeing an error popup that reads "The device OS version is too low."
I already tried setting all deployment targets to values below that of the iPhone OS and the watch. I even tried setting the watchOS Deployment Target, but none of these steps made a difference.
When looking this up, the only link I find has nothing to do with the Watch:
How to fix error : Error 0xe800007e: The device OS version is too low. ionic
Was anyone able to solve this?
The error, "The device OS version is too low," is reported erroneously since the watch app is installed on the device. If it doesn't show immediately, toggling the "Show on Device" button in the watch companion app, to uninstall and reinstall, will enable the app to be installed successfully.
I get the same problem that is described in this question. However, that problem dealt with the iOS simulator, not a physical device.
I'm not using the iOS Simulator. I'm deploying to an iPhone + Apple Watch.
If I attempt to run it on the simulator, it works just fine.
On the "Running WatchKit App on Apple Watch" build step, I get the following error:
Error Launching 'WatchKit Extension'
The operation couldn’t be completed. (FBSOpenApplicationErrorDomain error 3.)
What I've tried:
I tried reseting the iOS simulator and then running it on the device (not sure how that would help), but I still got the same error message.
I tried going in to iOS Settings > General > Device Management and ensuring that the app is "Verified".
Restarting Xcode didn't help either.
Deleting the app and reinstalling doesn't help.
I tried running the iOS app once to ensure there are no permissions issues on that end.
Xcode: 7.2
iPhone: iOS 9.2
Apple Watch: watchOS 2.1
This was a permissions issue on the Apple Watch.
To fix:
Launch the app once manually (not through Xcode).
You will see the following message:
Untrusted App Developer
Do you trust the developer "..." to run apps on your Apple Watch?
[Trust]
[Don't Trust]
Tap Trust.
Now you can run the app through Xcode with no issues.
Had same issue:
Go to settings on iphone
General > Device management
choose your developer app from list
click on trust
I have an app with an iOS Deployment Target of iOS 7.0, and I've added a WatchKit target. As expected, the WatchKit Extension has an iOS Deployment Target of 8.2. When I run the primary app on the iOS 8.2 simulator, everything works as-expected. However, if I try to run it on the iOS 8.1 simulator, Xcode reports: The operation couldn’t be completed. (LaunchServicesError error 0.)
The CoreSimulator.log file contains the following message:
com.apple.dt.Xcode[12181] : Error Domain=LaunchServicesError Code=0 "The operation couldn’t be completed. (LaunchServicesError error 0.)" UserInfo=0x7ff46e2dc980 {Error=AppexBundleUnknownExtensionPointIdentifier, ErrorDescription=Appex bundle at /Users//Library/Developer/CoreSimulator/Devices//data/Library/Caches/com.apple.mobile.installd.staging/temp.xmo2ks/extracted/InstallBug.app/PlugIns/InstallBug WatchKit Extension.appex with id com..InstallBug.watchkitextension specifies a value (com.apple.watchkit) for the NSExtensionPointIdentifier key in the NSExtension dictionary in its Info.plist that does not correspond to a known extension point.
I don't see any mention of this issue in the release notes, and I'm wondering if this is something that others have encountered. If so, is there something else that I need to configure to make this work? If not, I'll file a bug report.
Thanks.
This is a known issue with Xcode 6.2.
You can workaround it by adding a "MinimumOSVersion" = "8.2" key-value pair to your Apple Watch extensions's Info.plist file.
Users will have to be updated to iOS 8.2 in order to install and run a Watch App. Anyone not running iOS 8.2+ will not be prompted to install the Watch App and won't even know that it is available. There are several reasons for this.
The Apple Watch iOS App isn't available on iOS until iOS 8.2+
The Watch Extension APIs for an iOS app weren't available until iOS 8.2+
There is some additional information here.
Hopefully that helps shed some light.
I keep getting this error:
Catastrophic assertion failure
When I try starting the simulator (BlackBerry® Device Simulators v5.0.0.713 (9550)), am using BlackBerry Theme Studio 6.0. What can I do?