Its terminating even for apple demo code.
Refer the screen shot.
I have found that after initially installing the app and receiving this error, you should go into the simulator messages app and manually enable your messages app as it will be disabled by default. Once you enable it, it should work.
Related
Xcode "Run" operation fails to install a watchOS app on a real Apple Watch device with error description:
The host is not paired with the device.
Context:
First time ever trying to install a watchOS app from Xcode onto an Apple Watch device for testing/debugging
The watchOS app is an official Apple SwiftUI tutorial example
Assume latest versions of MacOS, Xcode, watchOS, Watch device, etc.
The selected scheme is the watchOS app target
The selected device is "[my Apple Watch name] via [my iPhone name]"
The Apple Watch is in fact paired with the companion iPhone, despite what the Xcode error says
The Apple Watch has not yet trusted this particular Xcode, Mac, developer account, or app. The Apple Watch should have received a "trust/don't trust" notification, but did not; this may be a bug on Apple's part.
However, we can force the notification to pop up by simply restarting the Apple Watch device. The Watch should receive the notification immediately upon restarting. Click "Trust" in the notification on the Watch. Then retry, from Xcode, the "Run" operation. The watchOS app should now install OK on the Apple Watch device.
What needs to be done is restarting both devices, iPhone and paired Apple Watch, connect iPhone to computer with cable. When the trust/don't trust notification appears on the Apple Watch or iPhone obviously choose 'trust'. Then the app will install again.
What it stops from running on your watch sometimes is if you have a simulator debug session open still. It says it can't install because there is another debug session running (but not on your watch..)! Closing this simulator session will allow you to install on your watch.
Other times xCode is building fine and thinks it's running the app on your watch, but it runs an old version and you don't see any changes made. Then you have to delete the app from your Apple Watch.
What also sometimes stops it from running on the Apple Watch are in Xcode the Preferences->Accounts->Profiles. Installing them manually will help in that case.
If nothing works uncouple your apple watch from your iPhone and recouple again.
Why isn't this still been resolved? I see people complaining about it for several of years now. Is this bug only related to standalone apps?
I am using xamarin.forms to do an app for ios and Android.
I am using Rg.popup as well.
The problem is: when I run the app in ios and before my rg.popup appear the system shows a system popup, my layout is strange...
How it can be
does Someone know how to solve?
Remote notification is not supported on Simulator, so system log an error about this and your code shows it with an alert. You need a real device to test remote notification.
To get rid of the alert view, find the code which shows the system alert in FailedToRegisterForRemoteNotifications method in AppDelegate.cs. Forbid it when the error code is 3010(which is for the error).
Up until today, I've been able to build, run, and debug my watch app and iOS app at the same time. When I build and run, the debugger attaches to the watch automatically. Then I have to manually attach the iOS debugger. I have been following these steps and they always worked perfectly. I can hit breakpoints on both on the watch and the phone (which is what I need to do to be able to debug things like sendMessage or applicationContext).
The problem now is that when I go to attach the iOS app to the debugger manually (via Debug -> Attach to Process), it doesn't show up in the likely targets or in applications at all, even though the app is running on the phone.
I checked my schemes and made sure that the targets were still correct- they are.
I even tried Debug -> Attach to Process with PID or Name. When I try to attach the iOS app by name, I get an error saying Will install Watch App called with bad bundle identifier '(null).
Why is my iOS app no longer a likely target? How can I get it to attach to the debugger again while my watch app is also attached?
I use another way to debug on watch app and iPhone app at the same time. I run this script when watch and iPhone simulators are running on my Mac. Then launch my watch app or iPhone app on the same simulators. I can observe both log at the same time.
P.S. These log are come from console, so you should use NSLog(), not print().
In CloudPebble, there is a setting for App Visibility:
What does "Only Visible When Companion App Running" mean exactly? Does it mean when the iOS/Android companion app isn't running, then the Pebble watchapp doesn't show up in the app list on the Pebble?
I tried to look for information on the App Metadata docs page, https://developer.pebble.com/guides/pebble-apps/app-structure/app-metadata/, but it's broken...
I tried the setting on a watchapp I have that has an iOS companion app, and the setting doesn't seem to do anything at all. When I forcequit my iOS app, the watchapp is still listed in the Pebble app list.
This metadata item causes the watch app to be hidden when the phone app can't communicated with the watch, and to be shown when it can. The reason it stays open is because apps that use the new PebbleKit on iOS are allowed to continue communicating over BLE, even when force closed.
I am using Xamarin.Forms.Labs to send SMS messages from my app. It works great on WP and Android but with the iOS it opens up the default texting screen and allows you to send a text but then I am unable to get back to my app. I click cancel or the iPhone button and reopen my app and it is still on the texting screen. Any ideas what I could be doing wrong or why it doesn't return to my app once I have finished texting? Is anyone else having this issue?
This was a bug in the iOS implementation. I just pushed a fix for it and you can use the latest code (master branch) to test it out.
https://github.com/XLabs/Xamarin-Forms-Labs/pull/498
I will get it included in the next release package.