Yes I reported this in the official Bug Report Form.
You could remove your login group and then it should disappear. However, if you have lots of other functionality that relies on a User being logged in like I do then that is pointless. The release of my app to live is blocked by this bug.
I test apps for a living and there’s no way I would release a native app without testing it on a real device first. Luckily at work I have a wide range of devices to test on and have 9.2.5 iOS but only on an iPhone 4S.
I tried to revert to 9.2.5 by downloading an .ipsw file but looks like Apple only let you revert back during a set time period which has now expired.
For mobile Safari you can download XCode/Simulator which will allow you to test the mobile site across multiple devices/iOS but this doesn’t work for the native app.
The trick would be to use the following plugin to set the cookievalue from the plugin and fetch/use it for all subsequent calls. If you wanna hack it out make sure you intercept ajax calls using a replacement function for the original ajax calls the inserts the value on each new request.
@emmanuel can you confirm if this is resolved on your side or in subsequent releases of iOS.
(amended 3rd party approach from django to bubble)
The fix for iOS that bubble has to implement on backend + app would be:
Bubble needs to generate a csrftoken (or equivalent auth token) and send the data to web-app via JsonResponse;
Use cookieMaster’s setCookieValue to set the csrftoken to the domain cookie.
The csrftoken can then be retrieved to send to bubble in subsequent calls.
btw, researching more this should have been fixed in iOS 11, but it seems to me that it may still be a large user base on iOS 10 for a long time. So to find a workaround for iOS10 should still be a priority!
There are new clues for how to fix iOS10 in the best possible way here: ios - Can I set the cookies to be used by a WKWebView? - Stack Overflow