I see 24 hours report completely broken and unreliable in AppStoreConnect Sales & Trends for more than a month. When I submit a complain, all they say is clear cookies and caches and restart the browser. Either the complain is not forwarded to engineering or engineering is not acknowledging the issue.
Search results for
ASWebAuthenticationSession cookie
1,295 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Facing the same issue on the 14. When I look at AudioStreamBasicDescription of the CMSampleBuffer that are received from videoChat mode on 14, I get this Optional( { mediaType:'soun' mediaSubType:'lpcm' mediaSpecific: { ASBD: { mSampleRate: 44100.000000 mFormatID: 'lpcm' mFormatFlags: 0xc mBytesPerPacket: 8 mFramesPerPacket: 1 mBytesPerFrame: 8 mChannelsPerFrame: 4 mBitsPerChannel: 16 } cookie: {(null)} ACL: {Mono} FormatList Array: { Index: 0 ChannelLayoutTag: 0x640001 ASBD: { mSampleRate: 44100.000000 mFormatID: 'lpcm' mFormatFlags: 0xc mBytesPerPacket: 8 mFramesPerPacket: 1 mBytesPerFrame: 8 mChannelsPerFrame: 4 mBitsPerChannel: 16 }} } extensions: {(null)} }) When I initialize audio session in default mode, the CMAudioFormatDescription of audio samples is Optional( { mediaType:'soun' mediaSubType:'lpcm' mediaSpecific: { ASBD: { mSampleRate: 44100.000000 mFormatID: 'lpcm' mFormatFlags: 0xc mBytesPerPacket: 2 mFramesPerPacket: 1 mBytesPerFrame: 2 mChannelsPerFrame: 1 mBitsPerChannel: 16 } cookie
Topic:
Media Technologies
SubTopic:
Audio
Tags:
Hello, We release an App Clip back in December 2020, and everything was working just fine for the longest time. However, sometime relatively recently, not exactly sure when it started, the Domain URL Status started showing this “Cannot Reach AASA File” error; and consequently, the App Clip invocation fails now. The API Validation Tool is saying “Error cannot parse app site association file” as the reason. We have not made any changes in the App / App Clip, and the associated domain is still set as appclips:mobileapp.caesars.com The Apple App Site Association file hasn’t been changed either, and the format still matches that specified on https://developer.apple.com/documentation/app_clips/associating_your_app_clip_with_your_website. The AASA file returns no problem in a browser and from curl command as you can see below: Last login: Tue Jul 12 09:11:11 on console curl -v https://mobileapp.caesars.com/.well-known/apple-app-site-association * Trying 192.230.66.155:443... * Connected to mobileapp.caesars.com (192
In versions of Safari going back at least a year, when the Develop menu is on, all cookies are expired hours after being set. I'm using Version 16.1 (18614.2.3.1.1) currently. I had the problem for a long time before discovering the cause (in a MacRumours forum post). I’d rather not have to keep using Chrome for development work, but that's what I have to do until this issue is resolved. Does anyone know of a workaround or at least whether the problem has been acknowledged?
Safari looses session cookies, so after some time (15-30 minutes) I have to login again. This happens for all my synced tabs with iOS and happens even if I use only macOS. It’s very annoying because I have to login again in a lot of services, multiple times a day.
It depends on what you're looking for. Do you want to use FIDO as an unphishable second factor to be added to a phishable first factor (e.g. a password)? Or are you looking to wholly remove phishability from accounts and use FIDO as a single factor? Do you want biometrics because theft of an unlocked device is one of the primary ways your accounts are getting compromised today, or because it checks a box about another factor? Does it have to be built in to the device, or do biometrics on an external security key meet these requirements? If you don't need something built in to the device, security keys have been around since long before passkeys. Safari introduced support for them a few years ago (so they work in SFSafariViewController and ASWebAuthenticationSession) and we introduced native API for them in iOS 15. If you have a requirement that is literally biometrics, you can enforce that only security keys with biometrics are used via attestation (though before you do so, you should consider the ex
Topic:
Privacy & Security
SubTopic:
General
Tags:
Any update on this? We use a webview to perform login and the webview shows a cookie banner, but we don't use those cookies to track.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I am currently trying to run my app in release mode on my iOS device and every time the app starts up, it only displays a white screen. In the device logs I see this when the app is first launched: Error loading metadata for com.outlit.app: Error Domain=ASDErrorDomain Code=513 Loading failed for '/private/var/containers/Bundle/Application/6C87729B-A97F-4D3E-BA9F-ADEADF6BD28A' UserInfo={NSDebugDescription=Loading failed for '/private/var/containers/Bundle/Application/6C87729B-A97F-4D3E-BA9F-ADEADF6BD28A', NSUnderlyingError=0x100e11a30 {Error Domain=MIInstallerErrorDomain Code=78 Failed to read iTunesMetadata.plist from /private/var/containers/Bundle/Application/6C87729B-A97F-4D3E-BA9F-ADEADF6BD28A/iTunesMetadata.plist UserInfo={NSLocalizedDescription=Failed to read iTunesMetadata.plist from /private/var/containers/Bundle/Application/6C87729B-A97F-4D3E-BA9F-ADEADF6BD28A/iTunesMetadata.plist, LegacyErrorString=InvalidiTunesMetadataPlist, FunctionName=+[MIStoreMetadata metadataFromPlistAtURL:error:], SourceFileLi
Hi, We have a client portal app, synching data with a CRM. The last version of our app has been refused for this reason : We noticed your app accesses web content you own where you collect cookies. Cookies may be used to track users, but you do not use App Tracking Transparency to request the user's permission before collecting data used to track. Thing is : we collect data for audience measuring only (using Matomo) ; there is no advertising, and no data-broker involved, no other 3rd-parties ; we do prompt users either to accept cookie or not, only to be compliant with GDPR ; we did not implement the App Tracking Transparency notification though. It's unclear to decide what we must do. The answer of Apple is : If you do not collect cookies for tracking purposes on iOS, remove the cookie prompts or revise them to clarify you do not track users. But we cannot remove the cookie prompt, because it's required for GDPR compliance. Any idea of how we can solve th
If you do not collect cookies for tracking purposes on iOS ... revise them to clarify you do not track users. Do this. (Are you hosting the Matomo server instance yourself?)
Topic:
App Store Distribution & Marketing
SubTopic:
General
Tags:
But we cannot remove the cookie prompt, because it's required for GDPR compliance. I don't think so. AFAIK, if you do not use cookies, you don't have to ask. https://gdpr.eu/cookies/ To comply with the regulations governing cookies under the GDPR and the ePrivacy Directive you must: Receive users’ consent before you use any cookies except strictly necessary cookies. Provide accurate and specific information about the data each cookie tracks and its purpose in plain language before consent is received. Document and store consent received from users. Allow users to access your service even if they refuse to allow the use of certain cookies Make it as easy for users to withdraw their consent as it was for them to give their consent in the first place. My reading of first bullet is that you need to ask only when you use cookies. Be cautious though: your site may set cookies that you don't know. There are tools to check if yo
Topic:
App Store Distribution & Marketing
SubTopic:
General
Tags:
Same issue. Lack of docs around this is pretty terrible. The best I've found is this (search for 7-day): https://webkit.org/blog/10218/full-third-party-cookie-blocking-and-more/ Additionally, Safari desktop doesn't appear to support Add to Home Screen...so that seems to imply that people using a offline first web app on Safari Desktop will always be at risk for data loss. Unacceptable! I have experimented with using the StorageManager persist option with Safari Desktop in order to mark persistence as protected. However, it appears this gets reset when the browser closes and again there's a lack of documentation so it's not even clear if this would help protect against the 7-day ITP timer. Without more documentation and clear direction from Apple, I'm basically forced to tell my users not to use Desktop Safari :(
Topic:
Safari & Web
SubTopic:
General
Tags:
Hi All. I am building a safari app extension which needs to make several HTTP requests from the background script. The HTTP requests need to use the Cookies that exist on my webpage. When I make the requests from my background script, I see 3 of my 4 cookies are added to the request cookie header, but the 4th cookie is not there. The 4th cookie has SameSite=Lax which seems to be the issue. When I manually change Lax to none, in my webpage's cookie storage, then the request goes through successfully from my background script. Does anyone know if there is a way to get/use cookies labeled as SameSite=Lax in my background script? I tried the broswer.cookies API, but it seems that the API will only retrieve non HttpOnly cookies, and my cookie has HttpOnly enabled as well, so this does not work. How can I make requests from my background script that need to use cookies from my webpage? P.S. This works in my chrome extension ju
I've solved this issue, I just had to clean cookies for the SFSafariViewController (I've done that in PHP)
Topic:
Programming Languages
SubTopic:
Swift
Tags:
I have the same issue and found no solution yet. But at least Mac OS Ventura Beta stopped deleting the cookies from the browser when the extension fails to get them. So there is some progress there, but the bug is still not solved.
Topic:
Safari & Web
SubTopic:
General
Tags: