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.
Related
I am trying to implement the FB comments plugin (https://developers.facebook.com/docs/plugins/comments/) on a website. It's loading fine, but on iOS Safari the user cannot click into the comments field. When trying to click into the field, a quick visual glitch happens, and then focus is lost.
On some phones, if I log into facebook in the same browser, this makes an alert appear, when clicking into the field, to allow facebook tracking. After accepting that I'm allowed to click into the field.
I haven't managed to find any info on this. It's working fine on desktop/laptop macs and PCs, android and in iOS Chrome. But specifically in iOS Safari (on some phones) it's bugging out.
Does anyone know anything about this bug and how to fix it?
It's the settings -> safari -> Hide IP Address (from trackers) switch that stops the FB plugins working!
We are currently developing a PWA for a client of ours. Everything has been going well, but while testing on iPhone (iOS 12.2) we are having an issue with the tags that have sms:123-456-7890 in the href. You get the "Safari cannot open this page because of the sms: tag" (paraphrasing).
If you are browsing the site via Safari (not in the PWA mode), the anchor tag works fine and your iMessage opens up with the number in it. But when you're in the PWA mode and click the link, you get a version of the message I mentioned above.
From doing research, this appears to be some sort of bug in the iOS 12.2 release, though not officially mentioned.
I'm curious if anyone has had any luck with a work-around for this issue?
Thanks in advance.
Edit..to add some code for the anchor tag....
123-456-7890
I've tried many different variations of the sms (with no // or ;), always same outcome when clicking it as a PWA. With Android, everything works fine in PWA mode.
I did find a workaround by using JavaScript
Code Example:
<a href="#" onclick="openSMSMobile();" >
function openSMSMobile(e) {
window.open('sms:1234567890', '_self');
return false;
}
And in case anyone is wondering, if you'd like to add text to the message body, you can use,
window.open('sms:1234567890&body=textGoesHere', '_self');
For Android you'll need,
window.open('sms:1234567890&body=textGoesHere', '_self');
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'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");
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.