I am trying to share data between Safari and a PWA/Standalone mode "Add to Homescreen" app in iPadOS 14 (not iOS) using cacheStorage.
I tried Pooya Estakhri's solution and it worked on iOS 14, but the same code did not work for iPadOS 14, even though the reference to Firt implies that cacheStorage should operate the same for iOS and iPadOS. It appears on iPadOS using caches.open("auth") that Safari and the PWA have separate cacheStorage.
Has anyone worked with this on iPadOS?
Related
I'm used to debugging my React Native (0.63.2) app using Safari's dev tools. I got an M1 Mac Mini last week and have since been unable to get the console or source tabs to show anything from the iOS simulator. Not sure if this is related to the new machine, or if I missed a setting. Any ideas?
I usually do Develop > Simulator > JSContents from Safari, and everything would show up fine. I can get logs in the terminal, but Safari's devtools are much easier to manage.
Installing and using the "Safari Technology Preview" from https://developer.apple.com/safari/download/ worked for me.
After doing a "Reset All Content And Settings.." on the simulator the setting to enable using the web inspector in safari has disappeared, and I have no idea how to get it back:
Does anyone have an idea how to get this back, and "remote" debug a webpage in the simulator again?
It seems that this option is not available in the simulated devices. Tip: If you want to connect the console from your desktop Safari, you will need the Technology Preview. the normal one does not discover the simulator (though it finds the real device normally)
In my case (macOS 10.14.3 and iOS 12.1 simulators), the setting isn't there, but is active by default. Open the simulator and you should see it in Safari under Develop.
i needed to restart desktop safari. might help.
Worked for me download new Safari:
IOS Simulator: 13.4
(Safari Technology Preview)
https://developer.apple.com/safari/download/
Safari Technology Preview
I just updated to Xcode 6.1 and my keyboard extension app, which was working fine with 6.0.x, is now not selectable via the nextinputmode button. This works fine on the actual device but not on the simulator. I can add the keyboard in settings with no trouble. Anyone else have this problem.
Update: This has been fixed in iOS 8.2 beta 2, according to release notes.
From iOS 8.1 beta release notes:
Known Issue 3rd party keyboards may not appear in Safari, Maps or 3rd
party apps on the Simulator.
Workaround: Keyboards should be testable in Calendar, Spotlight,
Contacts, and Photos.
This is what you are seeing.
I guess they were so busy fixing other bugs in the developer tools, they just didn't have time to fix ridiculous new bugs they introduced in 8.1.
Open a bug report, and maybe it will be fixed in 8.2.
We've been working on getting our app to work properly with all the changes in iOS 7. Particularly the colors and layouts of things. But these changes are still in development.
The version of our app in the app store has none of these modifications. When testing locally, it works on iOS 6 fine and looks horrible on iOS 7. Yet, upon downloading it from the app store and installing it on an iOS 7 iPad, it seems to work just fine -- just as it used to in iOS 6 (!). We are wondering if there is some "compatibility flag" that the app store folks can switch, which means "not ready for iOS 7 -- use compatibility mode"? I'm not sure how else to explain this. Wondering if anyone else knows?
Our app:
http://appstore.com/cedarssuite
Summary: running via the simulator on iOS 7 or on a development iPad that has iOS 7, the app looks horrible. But downloading the approved app store version and running on iOS 7, it works just fine. Why?
A note: This is no longer correct. Since February 2014, Apple only accepts SDK7 builds
That's normal. all the old apps work fine on new iOS versions since those app. Base SDK set to that old version. in your case (iOS 6.0). They will run using old sdks. But, when you built with the new sdk (Base SDK 7.0) they look horrible as you said and some times they crash. because of layout changes and controls behaviours in the new iOS.
You are only asked to build with the new sdk to take advantage of the new features.
keeping your app. built with the old versions doesn't seem to have disadvantages other than new features. since apple still accept publishing apps with old sdk back to 4.3.
If you set the base SDK < 7, it will use the old iOS 6 style. Of course, that basically requires you compile with an old version of Xcode, and you can't use iOS 7 features, even when running on iOS 7.
iOS 6 now supports uploading images via the <input type='file'> tag.
Is there any way to check for this support other than getting the user agent and checking whether the Safari version is 6.0 or greater? That seems kinda kludgy and prone to breaking if the user agent changes in the future. Also I'm not sure how it would work if users are using alternate browsers.
On my second generation iPod Touch (iOS 4.2.1), the following line of jQuery code evaluates as true in both Safari and Atomic Web Browser Lite and false in Opera Mini (since Opera Mini supports file uploads). On iPhone Simulator (iOS 6.0), it also evaluates as false.
$('#selector').prop('disabled')