![]() ![]() You must have enough storage and space on your device to let the Messenger app works properly. Check to have enough space on the phoneįacebook Messenger app keeps important files and caches on your device. So without further talking, let’s fix the Messenger something went wrong, please try again later problem. Thus I am pretty sure that you will get it fixed at the end of this article. But sometimes you will face an issue in the app, like the one you are having today, and look for an easy fix.Īnyways, just follow the below methods one by one. Messenger is of course an amazing instant messaging application. Mostly it can be your desired OS, thus resetting a device may be required. However, it can be something else and there is no solution for it but to uninstall and reinstall it again. Also, you are using an old Android device, app and device caches, etc. It could be Messenger servers, your internet connection, or you didn’t update the Messenger app for a long time. There are many reasons behind such an issue. Most users face this issue on the Messenger app and desktop variant. Reasons for Messenger Something Went Wrong Check if there is an update available for your device.Delete then install a new Messenger version.Check to have enough space on the phone.Fix Messenger Error Something Went Wrong. ![]() ![]() Reasons for Messenger Something Went Wrong.However, i solved it by adding these fields in my app.json. I had also the same issue after updating. Is anyone encountering this issue? Any suggestion on how to investigate this is appreciated! I tried with and without infoPlist, as above, while following other threads but the first rebuild after your message about fixing this crashed. There is no Facebook loader or that popup that appear asking you to login with facebook. The app works ok on Android even if Facebook app is installed or not, but on iOS simply the app crashes when the button is pressed and this line is called. I also tried for iOS system instead of native, but with native was working prior to this update. I am calling the function like below dispatching actions with redux on then and error cases.įacebook.logInWithReadPermissionsAsync('APP_ID', ) Basically after this update on iOS all my builds crashed when Facebook.logInWithReadPermissionsAsync is called. After the update I encountered another problem which I am not very sure how to resolve. I was watching this thread and I can confirm that the error was visible in my case too. The only way to get back to our app is to cancel, and of course the login process will fail. Expected BehaviorĪfter logging in with Facebook, you are redirected to our app and the login process is executed Actual BehaviorĮven after logging in on the Facebook app, it behaves like staying in the Facebook app. It’s pretty strange because it’s quite strange behavior and it hurts user acquisition opportunities. Must be logged out of Facebook in the browser, but logged in in the Facebook appįacebook.logInWithReadPermissionsAsync, doesn’t come back to our app after flying to Facebook app.įor now it only occurs on iOS standalone. IOS Standalone AND iOS Expo Client Steps to Reproduce Watchman: 4.9.0 - /usr/local/bin/watchman ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |