aryehsanders

Results 9 comments of aryehsanders

Just checking in to see if there's an intention to fix this since there seems to be no activity on this issue. The official [Dropbox HTTP documentation](https://www.dropbox.com/developers/documentation/http/documentation) in the section...

As a workaround, `new Dropbox()` accepts a `fetch` parameter. I passed a function that modifies the request to fit the requirements to skip the preflight, and it seems to work...

Thanks for responding; sorry I didn't notice sooner. This isn't a substitute for using our development code with real Firebase; now that some browsers have disabled third-party cookies, it has...

Just to be thorough, I did test with the emulator anyway, and sure enough, it doesn't work for auth in Firefox because of the third-party cookie partitioning change that lead...

If code would make the issue clearer - a small patch (untested!) in handler.ts would fix this: Instead of: ``` return `https://${config.authDomain}/${WIDGET_PATH}`; ``` Replace with: ``` const isLocalhost = config.authDomain.split(':')[0]...

I can provide the whole HAR file, but it's really not helpful. Firefox itself explains in the dev console: > Partitioned cookie or storage access was provided to “http://127.0.0.1:9099/emulator/auth/iframe?apiKey=AIzaSyDQDLCIq5syV05gAZTkwwjXMHaQP5x17IA&appName=%5BDEFAULT%5D-firebaseui-temp&v=9.22.1&eid=p&usegapi=1&jsh=m%3B%2F_%2Fscs%2Fabc-static%2F_%2Fjs%2Fk%3Dgapi.lb.en.S9zOXUg9rrA.O%2Fd%3D1%2Frs%3DAHpOoo-AXjUK4hNAaKzui0P9Fr9nG2_yZQ%2Fm%3D__features__#id=I0_1691412046814&_gfid=I0_1691412046814&parent=http%3A%2F%2Flocalhost%3A5000&pfname=&rpctoken=18705812” because...

Just adding another stack trace that appears to be the same issue: ``` 2024-07-30 16:07:33 sync INFO: Syncing ↓ 3/3 2024-07-30 16:07:33 sync INFO: Up to date 2024-07-30 16:07:33 manager...

The route_access_denied issue has been discussed on the Dropbox Forums, with no resolution yet: https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/route-access-denied/td-p/785422

And yesterday it was updated with a message from Dropbox staff that it has been fixed: > That team has deployed a fix to address this. Please let us know...