I know that ASWebAuthenticationSession usually is used with OAuth and similar protocols, but now I' interested, does ASWebAuthenticationSession supports other auth types? I've made such tests (iOS 14.5, Xcode 12.5.1): Tested ASWebAuthenticationSession with kerberos/negotiate URL (with callback scheme http) - SFSafariViewController loads error page with 401 error and no alert for creds; completion handler of ASWebAuthenticationSession is not called; Tested ASWebAuthenticationSession with NTLM, Digest and Basic URLs (with callback scheme http) - SFSafariViewController shows alert for creds; with correct creds content is shown; completion handler of ASWebAuthenticationSession also is not called; Performed the same test with SFSafariViewController - same results. Do I understand correctly, that ASWebAuthenticationSession doesn't support such auth types, but SFSafariViewController supports them? Why SFSafariViewController doesn't show alert for creds i
Search results for
ASWebAuthenticationSession cookie
1,297 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I've just started using the Find My app and it has limitations I don't like (or maybe I don't understand how to use the app.) On the left side of the app is a pane that contains either People, Devices, or Items. But I can't resize the pane (larger, to the right) to be able to read more data in that pane. Most apps, like Safari, allow me to resize the left pane. Why does this app prohibit that common feature? Also, I'd like each item in the pane to show more information. As it is now, I have to click on the item in the pane then read the details in the pop-up on the right pane, but if that doesn't show what I want, I have to click on the info symbol popup button to get more information. And then the pop-up window is in such a small font on my screen, and the text is printed in a dark-grey on light-grey background, it's very hard to read on a 4K monitor. And the app doesn't let me resize the text (Safari allows me to press keys to make the interface more readable.) Apple makes such a big deal about Accessibilit
I have seen a similar issue with my released application. When a user starts an ASWebAuthenticationSession Chrome does not fulfill the authentication session at all. It does not even open the website that it should open. I think ASWebAuthentication should default to Safari just to make sure that it works
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I am trying to download app content from a password protected directory of a website served by Apache24. The directory is protected using the following configuration segment: <Directory <directory path> AuthType Basic AuthName Restricted Content AuthUserFile <password file path>.htpasswd Require valid-user </Directory> Here is my swift code (running on latest betas of iOS15 or macOS12) class Downloader: NSObject { lazy var downloadSession: URLSession = { // Setup configuration let configuration = URLSessionConfiguration.default configuration.allowsCellularAccess = true configuration.timeoutIntervalForResource = 60 configuration.waitsForConnectivity = true // Add authorisation header to handle credentials let user = ***** let password = ****** let userPasswordData = (user):(password).data(using: .utf8) let base64EncodedCredential = userPasswordData!.base64EncodedString(options: Data.Base64EncodingOptions.init(rawValue: 0)) let authString = Basic (base64EncodedCredential) // Add authorisati
Topic:
App & System Services
SubTopic:
General
Tags:
On demand resources
Security
CFNetwork
Foundation
I'm not sure I understand this. Apple is saying that they rejected your submission because your app accesses web content you own where you collect cookies. But you are concluding that the issue relates to Firebase somehow. Can you explain why you are connecting cookies to Firebase? Not saying that you are incorrect, just that I don't understand the linkage between the two. We might have a similar issue, so I'm trying to get out in front of of this before it happens. Thanks and good luck. I'll post back to share any additional information that we get during our review process.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
We're seeing Chrome browser crashing after using ASWebAuthenticationSession to authenticate. While the authentication succeeds, all the user's browser tabs are terminated and upon re-opening Chrome, it shows a popup message: Chrome didn’t shut down correctly. System logs indicates that Chrome crashed (core dumped) with a Security Exception with macOS error code -67052.
Same issue here. I'm very disappointed with apple. I was happy with my QHD display and any other machine other than m1. are there any developers to solve this kind of showstopper issue right now? at least apple shoud answer and let us know the plan! what a shame. it's been a year. don't waste your time to add minor cookie functions. FIX THIS ISSUE FIRST!!!
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Our app uses Firebase Analytics as well as Firebase Crashlytics. We host no ads, nor intentionally track users. Analytics and Crashlytics are disabled by default and we ask the consent to enable these on our own default consent pages that are shown on app start. Recently the app updates have been getting rejected with the following message: Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing We noticed your app accesses web content you own where you collect cookies. However, you do not use App Tracking Transparency to request the user's permission before collecting data used to track. Collecting cookies is a form of tracking. Starting with iOS 14.5, apps on the App Store need to receive the user’s permission through the AppTrackingTransparency framework before collecting data used to track them. Next Steps Follow these steps to resolve this issue: If you haven't already, update your app privacy information in App Store Connect to disclose that you track users. You must have the Account
I have built this reactjs app the get cookie function wont work with Iphones and it return blank page it works fine with android and computers but not in iphones here is the javascript code for getting the cookie and also let me remind that I am using react redux ass well the code is in store.js function getCookie(name) { const value = `; ${document.cookie}`; const parts = value.split(`; ${name}=`); if (parts.length === 2) return parts.pop().split(;).shift(); } const userInfoFromStorage = getCookie(userInfo) ? JSON.parse(getCookie(userInfo)) : null; const initialState = { userLogin: { userInfo: userInfoFromStorage, }, }; const middleware = [thunk]; const store = createStore( reducer, initialState, composeWithDevTools(applyMiddleware(...middleware)) ); export default store; please help me :)
The IOS version that displays the webview is 14, and the node version of the server receiving the request is 10.0.0. About the webview simulator : (Mozilla/5.0 (iPhone; CPU iPhone OS 14_4 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148) In Android, the session value is delivered well, but when a web page is opened with WKWebview in IOS, the session value in the cookie is initialized in the middle. The node server is sending and receiving session information using the cookie-session library, and the web page front was developed with vue. I'm not sure exactly what the problem is, so I'm asking. The log is attached below. At first, the session value is properly entered in the request header as shown below and delivered. { name: Cookie, value: session={VALUE}; session.sig={VALUE}; TS0154565f={VALUE} }, However, in the next API call, the session value is passed well in the request, but the { name: Set-Cookie, value: session.sig=; path=/; expires=Thu, 01 Jan
I'm working on an app made in React Native with Expo. It uses a web view to show the site in the app. Everything worked well, but when I submitted my app to the App Store, it got rejected. The mail said: We noticed you collect data to track after the user selects Ask App Not to Track on the App Tracking Transparency permission request. Specifically, we noticed your app accesses web content you own and collects cookies for tracking after the user asked you not to track them. After that, using the expo tracking transparency library, I added a permission request to track data. If the user doesn't accept it, I disable third party cookies on the web view. After submitting again to the App Store, I got the exact same message. I don't know what to do, because I can't control the site, and I'm limited to the React Native web view props Maybe, I could enable incognito mode if the user doesn't want the app to track, but I'm not sure if this will be accepted too. Thanks in advance
I got clone to a repo and I installed node modules correctly without any errors, but when I run pod install in the command line, I get that error, Ignoring unf_ext-0.0.7.6 because its extensions are not built. Try: gem pristine unf_ext --version 0.0.7.6 Auto-linking React Native modules for target maltevinder: RNCAsyncStorage, RNCMaskedView, RNDateTimePicker, RNFastImage, RNGestureHandler, RNReanimated, RNScreens, RNVectorIcons, lottie-ios, lottie-react-native, react-native-cookies, react-native-document-picker, react-native-restart, and react-native-safe-area-context Analyzing dependencies Fetching podspec for DoubleConversion from ../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec Fetching podspec for Folly from ../node_modules/react-native/third-party-podspecs/Folly.podspec Fetching podspec for glog from ../node_modules/react-native/third-party-podspecs/glog.podspec [!] No podspec found for react-native-image-picker in ../node_modules/react-native-image-picker That's my Pod
Hi, I am working on automation tests for Safari webextension. Currently if I install webextension and open Safari instance, then go to simple page that set cookies, webextension can pick it up. In case I start tests using safaridriver, it opens Safari instance, opens simple page that set cookies, but when I click on webextension icon, then click Stop session, I see webextension did not pick up cookies. I am checking it on Safari 14.1.1 and macOS Big Sur. Same behavior I see on Safari Technology Preview. Can someone help me with it? Link with WDIO project example - https://github.com/idem7x/safaribug.
Its been noticed post upgrade to Big Sur our production application user cookies are not getting auto deleted during logout from our application, whereas this was working as expected before the upgrade (Catalina and safari 13.x.). The alternate approach we had is to clear the the cookies manually and restart the browser window. Is this is a bug in Safari 14.1? if not what are your recommendations to delete the cookies pragmatically.
I am deliberately using host-based virtual network to analyze potentially malicious binary, thus internet access is switched off. The cause is likely related to a previous post https://developer.apple.com/forums/thread/111225. Suggested workaround to return 127.0.0.1 from my local resolver did not help. The setup I got is I am using local DNS resolver to answer all domain queries. Domains that binary is using to connect to are dummy-resolving fine. Browsing to these using curl/Chrome works fine. It resolves into my webserver instance which returns desired response. However, when I execute binary itself, it fails with kCFErrorDomainCFNetwork CFNETWORK_DIAGNOSTICS is below: Filtering the log data using process == Installer AND composedMessage CONTAINS CFNetwork Timestamp Thread Type Activity PID TTL 2021-08-12 01:33:01.138319-0700 0x15b2 Default 0x0 622 0 Installer: (CFNetwork) [com.apple.CFNetwork:Diagnostics] CFNetwork Diagnostics [3:1] 01:33:01.138 { Begin Connect to cookied: (null) Requested versio