I'm making a mobile game using Unity3D 5.1.4, and inside my game I'd like the players to be able to open up my Facebook fanpage.
I have implemented it using this code:
Application.OpenURL("fb://page/442219965978230");
On Android it works fine, however the problem is on iOS.
I tested it on my iPad Air 2, iOS 9.2.
The Facebook app opened for a short moment, but then closed by itself.
This happens ONLY when the user is already logged into his Facebook account.
There was no error log when I checked in XCode...
After trying other games, I found out that opening Facebook would show a permission dialog "[Appname] wants to open Facebook", while in my game that dialog was never shown.
Is this what's causing the force close? Or something else?
I suspect it has something to do with iOS 9, isn't it?
If so, what do I need to do to fix it?
Change page to profile. For some reason, this is the fix for this problem.
Application.OpenURL("fb://profile/442219965978230");
Related
My App is in production now, and within my app I create a Universal link using branch.io and share it to other users using for example iMessage. Example link below I got from my friend is below:
I have the app from App Store installed on both devices: iPad and iPhone. Now the above link I tap on iPad and everything is fine. My App is opened I can catch the link:)
But when I tap it on iPhone the result is following:
Why? Shouldnt it works the same way on both: iPad and iPhone? I do not know what is wrong here... Any questions? I can change and add additional info here to help the solve the problem.
This is how I defined it in dashboard of branch.io:
You are encountering a new behavior introduced with iOS 10.3. The pop-up you are seeing will open the app now only if the user responds to the pop-up alert affirmatively. You must have not yet updated your iPad.
There is an unexpected issue with this new behavior beyond the obvious:
if the user taps "Cancel" on the pop-up alert, he or she will be stuck on a blank page in Safari. To improve this experience I recommend setting the $ios_passive_deepview parameter to the key of a Deepview of your choice (branch_default is the default, I believe).
I have a Problem. On Android, Chrome Mobile Devices when i open my website from the Facebook APP my popup is working. e(Popunder)... But when i open the same on my IPhone, iOS, it redirects automatic to about:blank!
Does anyone know this problem?
Regards
Regina
EDIT:
Okay.
1) My Website has got an Popunder script on it from Adcash. 2) When i open the site on iOS, Android, or Desktop the pounder is working very fine. 3) When i open the site on Android, Chrome, etc. from the Facebook inApp is working fine.
But !!!
When i open the site from iOS(IPhone) from the Facebook inApp it will redirect to about:blank empty page...
Do you understand know the problem? I tried many weeks to solve this issue but i don't know why it is so.
I've come across this issue.
On iOS only, and on either Facebook or Twitter's in-app browser
Tap on an article/link
Within the article, tap on a link that goes to a different domain and has a target=_blank attribute
The window is now white with the url set to about:blank
This issue is cross-product and not only Facebook's end.
The only method to address this issue was to change the target attribute from _blank to _self.
I'm trying to see if other people have had this issue or even addressed anywhere else, but this post is the closest I've come across to seeing it addressed.
I want to redirect the user of our iOS App to our Twitter profile page with the URL scheme:
twitter://user?screen_name=SCREEN_NAME
I recently noticed that this opens the Twitter app as expected but it shows a screen as if I used it for the first time:
The app is also completely frozen, I can't touch anything. If I keep the app open and klick on the UIButton in our app again, the profile will be shown correctly but still without being able to touch anything.
The only way I can get this to work is if I start the Twitter app before and let it open (in background). If I select the UIButton in our app now, everything works fine, the profile is shown and I'm able to interact with the Twitter app.
I think that there might be a problem of the Twitter app to handle such URL schemes on app start, but works when the app is already running.
Does anyone else experience this problem or have a solution for this issue?
Weirdly deleting and reinstalling the Twitter app fixed this problem. Still don't know why it happened though...
We started using Facebook's SDK in our game which was made with Unity.
We are trying to post "brag posts" when people win against their friends, and we use FB.Feed with the friend's ID in the "to" parameter.
In iOS devices running with an older FB app version, a small popup opens up inside the game - and it works perfectly well.
However on devices running the newest FB app version, when we call this function the FB app is opened, completely losing focus from our game, and an incorrect brag post is shown and attempts to post it on the user's wall (instead of on the friend's wall).
Anyone else had this problem and figured out how to fix it?
Thanks
I'll look into whether the feed dialog changed in newer version of the facebook app. In the meantime here's a workaround. In the exported xcode project, open FbUnityInterface.mm and go to line 46.
You should see the code
self.dialogMode = NativeDialogModes::FAST_APP_SWITCH_SHARE_DIALOG;
change that to
self.dialogMode = NativeDialogModes::WEBVIEW_DIALOG_MODE;
This will force the sdk to use webview dialogs instead of the one from the facebook app.
I am trying to use the SoundCloud SC.Connect mobile friendly pop-up as Shown in the Javascript SDK examples.
It works on all desktop browsers, however on Safari iOS 5.0 iPod Touch, latest model, it doesn't. It gets to the 'this popup should close in a few seconds' message and no further.
Other iOS devices have not been tested.
Is anyone else experiencing this issue?
Thanks
thanks for reporting this!
Seems like some new restrictions in mobile safari on iOS5 are preventing the
closing of the popup window automatically.
So far the only workaround I found was adding a link in the callback.html
Close
that the user has to click to finish the authorization.
I'll try to come up with a more elegant solution and let you know about it, but this is at least a quick fix for now.