I package the wearable app into the handheld app manually by using eclipse wearable app had installed successfully.But when syncing data from handheld to wear, it is nothing to happen.I am sure the sign key was same.
Strangely, Using the same code I debugging install wearable app over bluetooth, data sync ok. I am sure that sending message was success on mobile, i guess onMessageReceived() didn't work on wear.I don't know.
Somebody help me, thanks!
Related
I'm trying to add a notification service extension to my Xamarin iOS so that I can receive silent notifications. I'm using OneSignal and have followed their instructions and set up everything that I think is required:
App bundle id = com.abc.abcapp
Extension bundle ID = com.abc.abcapp.OneSignalNotificationServiceExtension
Added extension project reference to app
Enabled App Groups in app & extension and set to group.com.abc.abcapp.onesignal (also registered this in Apple developer portal)
Using Automatic Provisioning for both, which seems to have registered everything properly
It builds fine. I have Visual Studio 2022 deploy it to a physical iPhone plugged into my computer. It deploys fine. But notifications don't appear to go to the extension. They just go to the App, which limit the number of silent notifications I can send to a device to a few an hour.
Some possibly useful debugging?
Getting the phone's device log in Visual Studio is really hit or miss but at one point I did see this err:
Library Validation failed: Rejecting '/private/var/containers/Bundle/Application/11D98889-9C2C-4218-A2C8-227C93CBD579/Abc.app/PlugIns/OneSignalNotificationServiceExtension.appex/libOneSignalNotificationServiceExtension.dll.dylib' (Team ID: none, platform: no) for process 'OneSignalNotific(2868)' (Team ID: CJTV38PNRD, platform: no), reason: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.
When I try to build this in MS App Center, it doesn't recognize that I have an extension and doesn't let me associate a second profile or cert. (which I think it's supposed to do?)
According to documentation You can’t modify silent notifications or those that only play a sound or badge the app’s icon.
enter image description here
I built ipa file with react native expo and i attempted testing on devices.
I connected my own iphone to mac and used xcode + button for upload.
But i got a this message that "Unable to install (appname)" . Can I test the app(that built by expo) on the my own device?? I already registered apple developer accounts at yesterday.
According to a thread on developer.apple.com, this issue got resolved after the iOS version 13.4. Please review your developer account and it's license, as it usually happen with non-paid developer account.
Quick way to testing your app, upload your ipa on diawi.com and with QR Scan or Share link, you can download and install app on your device.
I have configured the Appceter Xamarin.ios for sending notifications to iOS devices. I entered everything as is mentioned in AppCenter but when I send notifications, it says Sending and looks like its stuck there. I don't know what the issue can be. Any ideas here?
As you can read here, push notifications cannot be tested on a simulator for iOS. You will need to test it on a device
Because of configuration requirements for iOS push notifications, you
must deploy and test the sample application on a physical iOS device
(iPhone or iPad) instead of in the simulator.
I just published my app for wear devices, its the Watch Face, don't have any UI for phone app. I uploaded to the Google Play.
But it says This app is incompatible with your device. To all users or Devices.
Anyone have idea?
Since Android Wear application are only in sync with a handheld device, it needs to have a corresponding application in the handheld device.
Let me make it little more clear:
To install anything on Android Wear, you need to have corresponding application for mobile, which will sync up its corresponding wear part and install the same on wear.
So go ahead develop a dummy kind of an application for handheld.
According to the official documentation, in order to publish a wearable app without a phone app component, you need to raise your minimum target SDK version to 2.0.
Source: https://developer.android.com/training/wearables/apps/standalone-apps.html
My device is registered in the distribution provisioning profile, the profile is uploaded to Test Flight, a build is prepared and sent to my device. I got the email, clicked in the Install button, and I start getting a screen with button that says Reconnect Device, I connected my device through Safari, logged in to test flight and TF said that my device now is successfully connectedso I build another ipa and sent it to my device, but gotting always the same issue, Reconnect Device button. Am I missing something? Thank you.
I had the same trouble recently. Tried reconnected my devices (2) a few times, only to find out that their UDIDs got changed in TestFlight on uploading a new build, so the build was still not available for my devices. I tried removing wrong UDID's in TestFlight, keeping the right ones, but it didn't solve the problem.
What finally helped was this:
removing all apps installed from TestFlight on all of my devices
removing all UDID's from my TestFlight account
reconnecting my devices to TestFlight
Let me know if it helps in your case. Good luck!
We have received a lot of "reconnect device" messages on iPhones lately and, at least for one tester, we have found a workaround. Instead of following the email links, the user had do install the build from within the TestFlight mobile app.