I've been trying to get the OneSignal Xamarin SDK setup complete to test it out for an app I'm working on, but I've run into a wall after finishing the setup according to the instructions here OneSignal Documentation - Xamarin SDK Setup. When I go to test the app on the Xamarin Live Player on my phone.
I get a visualization error as follows:
Didn't find class "com.onesignal.OneSignal" on path: DexPathList[[zip file "/data/app/com.xamarin.live-n4xLe1XSCWWGOA9DcqcG-g==/base.apk"],nativeLibraryDirectories=[/data/app/com.xamarin.live-n4xLe1XSCWWGOA9DcqcG-g==/lib/arm,/data/app/com.xamarin.live-n4xLe1XSCWWGOA9cqcG-g==/base.apk!/lib/armeabi-v7a,/system/lib,/vendor/lib]] (ClassNotFoundException)
I'm at a total loss at how to proceed, no where else does this error pop up when I search for other solutions. And to top it off, the code works perfectly on the emulator built into Visual Studio. I can send notifications through the OneSignal website and receive them on the emulator instantly with no issues. But for some reason, it fails every time on my phone with that same error.
SushiHangover gave me the solution.
Related
My app is an Ionic capacitor angular project. It is very simple, just to read QR codes. Testing on android studio works without problem, the app open the camera, read the QR and present the correct results. When I deployed to Firebase, the process finish without any problem and the app is on the screen of my device (tablet), when i tried to begin to scan, the camera is not open, no error messages..nothing, what could be the error? this also happened in other device(my phone), exactly the same behavoir, camera is not open. I would appreciate your comments.
Tried in different devices and same problem. Why in android studio it works and not after deploy in firebase?
We have a published app in the Teams App Store.
We have implemented BarCode scanner feature in the task module and it is working fine. However when code is scanned we want to close the task module right away by executing microsoftTeams.tasks.submitTask();
This method is working great on Android and it closes the task module window, but it does not work on IOS.
On IOS we are receiving this error:
This call is not allowed in the 'content' context.
We have also tried to add parameters result and appIds but it didn't help.
IOS app version:
Microsoft Teams
Version: 3.16.0
Build: 3.16.77.2021163502/1004 (general)
Calling Version: 2021.34.01.8
Release Branch: 2021Sep-T1
Any help would be appreciated.
I also ran into this issue. To fix it, I downgraded #microsoft/teams-js from 1.11 to 1.10 and the modal began working as expected in iOS.
I have developed an app and integrated with Admob using cordova-admob-free. It works fine when the release apk is installed to any device (test or not). It also works when the app is installed to a test device from play store.
However, in any other device that installed the app from the Play Store, ads are not shown and LOAD_FAIL event fires with error code: 3 and reason: No fill.
My admob profile is complete. (I have an older app with working ads)
I have the <variable name="PLAY_SERVICES_VERSION" value="11.0.0" /> dependency in the config.xml file. (I also tried the version 17.0.0)
I created app-ads.txt in my developer website
I tried to create new ad units and use them
I didn't try to remove the app from the store and create another one as it takes too long to be confirmed.
I couldn't get any reply from the Admob support or github repo. I appreciate any help. Thanks.
Since the ads was working when installed from apk, I thought the case is different from newly published apps. However, it just begin to work after 8-10 days from publication. As the other "no fill" error cases, the solution was just waiting.
I have a Xamarin.Forms Android app on the Google Play store. An overwhelming amount of users are leaving 1 star app reviews of my app saying that the app is "Freezing." They say that nothing happens when they click on a button in the apps UI. I have made doubly sure that no processes are running on the UI Thread that might hold up the UI. I have not been able to recreate this "Freezing" behavior personally. There are also no crash or ANR reports in the Google Play Console (at least not enough to make up for the amount of negative reviews I'm receiving). Has anyone else faced this problem?
Useful Info:
Xamarin.Forms Version: 4.8.0.1560
There is no discrimination between the Freezing behavior and users' Android API Version
The issue is not happening (or is not being reported) on the iOS app.
Do you have a physical Android device to deploy to? Take the apk and side load it, or download from the store, don't use VS to deploy the app on your device.
I had a similar issue and it was the code shrinker in VS. The released version with the code shrinker enabled, caused the app to freeze immediately after the splash screen.
You can disable it by selecting 'nothing' in the code shrinker box in VS.
Trying to implement the Google Sign-In for IOS in a Xamarin project. Right on the Google page where it generates your GoogleService-Info.plist file, it says, "Insure you have CocoaPods installed and configured for your project. In you Podfile, include the following: pod 'Google/SignIn'".
And sure enough, the log on the Mac shows a similar error when going through the initial configuration.
But, I can't find anything that really tells me how to add a "Podfile" to a Xamarin IOS project (from within Visual Studio 2017, running on Windows 10).
So, when it comes time to actually click the Sign-In with Google button, in an IOS 10.3 IPhone 6 simulator, it throws an exception,
"Foundation.MonoTouchException: Objective-C exception thrown. Name:
NSInvalidArgumentException Reason: -[__NSCFString
countByEnumeratingWithState:objects:count:]: unrecognized selector
sent to instance 0x608000047200".
I can only hope it is really because of a missing component that the Podfile is supposed to resolve.
Saw a sample from a year ago that supposedly worked, but with what seems to be current right now, I can't get it to.
Update:
The sample I am trying to use, creates a custom class for the View so it can implement a custom Renderer, and a custom class for the page, again, so it can implement a custom Renderer. The View Renderer simply does:
signInButton = new SignInButton();
signInButton.Style = ButtonStyle.Wide;
signInButton.ColorScheme = ButtonColorScheme.Dark;
SetNativeControl(signInButton);
The Google button shows up, but when you click, you get the exception listed above.
A recent update to Xamarin required an update to XCode. With the update to XCode 9,the problem went away, and Google authorization is working.