Xamarin.Forms.Labs iOS SMS texting issue - xamarin

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.

Related

WatchOS 6 notifications not arriving

I'm wondering if there's a known bug in WatchOS 6.1.1 regarding local notifications triggered from the watch?
I have an app that I developed about two years ago on watchOS 4. It would send local notifications from the watch during background processing. It worked great. The code sat for about two years and I was asked to update it. Since updating, I cannot get local notifications from my watch to work when I distribute builds through TestFlight. When I run the app through Xcode it works (both with the Debug and Release schemes). I saved logs in the watch app that show that the UNUserNotifications.current.add() does not pass an error into its completion handler. I can get local notifications from the handset in TestFlight builds to work and I can mirror those on the watch. But I cannot get local watch notifications to work. Does anyone have any idea why this might be? Is there a known bug? Have local watch notifications changed in a breaking way since watchOS 4?
I've found my issue. I think it's a new bug in watchOS6. It seems that permissions aren't being properly communicated from the handset to the watch. After giving permission for notifications on the handset, I would check for notification permissions on the watch and get .notDetermined. Strangely, if I downloaded the handset app and quickly gave notification permissions BEFORE the watch app had finished downloading, then it properly received notification permissions. I fixed this by simply requesting notification permissions on both the handset and the watch.

Conflit with systems popup of IOS and rg.plugin.popup

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).

iOS 10 Notification Service Extension

I'm working on the iOS 10 APNs function, trying to add Notification Service Extension to an existing App, add the function of pushing an image to the App.
After the extension was added, it did receive the pushed message. But couldn't receive the image, the function(wrote in the extension) of downloading the pushed image didn't execute during debugging. I checked the content in the App package, confirmed that the extension was installed in the App, it just didn't work.
What made me confused was that: I built a new testing project with same bundle id. The testing app could receive the pushed message and show the image correctly.(please see below screen shot)
What's wrong with the existing project? I tried to find the difference between the existing project and the testing project, yet found nothing in the code, setting, environment.
Does anyone encountered this before? I have been struggling in this for a week...
reference:
WWDC 2016 APNS Guide: https://willowtreeapps.com/ideas/wwdc-2016-rich-notifications-in-ios-10
Apple notification guide:https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ModifyingNotifications.html#//apple_ref/doc/uid/TP40008194-CH16-SW1
Finally this bug was fixed, please see the attached image. XCode recommends setting the architecture as automatic and I did so, then the notification service extension worked and could receive the pushed image. I don't know why this setting caused the problem, but I'm sure it works.

iOS 9 (13A340) remote notification not working

I am testing an app on iOS 9 (13A340) on iPhone 6, mainly the remote notification part. The remote push notification generated from AWS SNS cannot be received by the app, though the same app on iOS 8 works as expected. Is this due to the beta version of the iOS 9 or?
Thanks for any tip.
/Leonard
I have tried remaking the APSN development certificate and etc. and then it starts working, although I don't know what problem really was.
This didReceiveRemoteNotification method may also be called if a “silent/background” notification is received. As such, you should also enable “Background Modes: Remote Notifications” in the target capabilities panel (or else you’ll see warnings in the console).
Read more: http://www.intertech.com/Blog/push-notifications-tutorial-for-ios-9/#ixzz3tH8pRbz0
check image description here

Local Notification only appearing in Notification Center when app is open on iPhone

I'm having a strange issue. My UILocalNotifications are only appearing in the Notification Center when the app is open. If I have the iPhone at the launch screen they don't appear. The icon badge numbers from the notifications do appear though. The exact same code works perfectly on the iPad version of the app. I've verified that the body text is getting set correctly. The app is enabled in Notification Center with all options on as well.
If I have the app open and then tap home to leave the it, the notification disappears from Notification Center as well.
Has anyone else seen this?
Thanks,
Jason
My bad, missed one piece of code when merging from the iPad version.
Jason

Resources