Fixed
Status Update
No update yet.
Comments
yb...@google.com
Hello
This feature request has been forwarded to the product management team. You can track this thread to post any further comments or check the updates regarding this feature request. However we can't provide you with any ETA at this point.
This feature request has been forwarded to the product management team. You can track this thread to post any further comments or check the updates regarding this feature request. However we can't provide you with any ETA at this point.
se...@gmail.com
+1, We cannot create AJAX requests to APIs on a subdomain that are behind IAP because of this. The IAP seems to ignore the "Allowed JavaScript Origins" in the OAuth Client ID settings, it should be sending an Access-Control-Allow-Origin: <list of allowed origins> on the 302 redirect.
Example:
Failed to loadhttps://api.staging.example.com/endpoint : Redirect from 'https://api.staging.example.com/endpoint ' to 'https://accounts.google.com/o/oauth2/v2/auth?client_id=.. .' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://staging.example.com ' is therefore not allowed access.
Example:
Failed to load
se...@gmail.com
We ran into the same problem, which seems to make IAP unusable when serving an API.
Hopefully this can be solved quickly
(GCP support ticket [#16518176])
Hopefully this can be solved quickly
(GCP support ticket [#16518176])
yb...@google.com
sh...@google.com
da...@google.com
Hi, I also ran into the problem of CORS not supporting IAP. Here's my workaround, in case anyone else finds it useful.
In the same GCP project I have two App Engine services:
- A UI server
- An API server
The UI server makes calls to the API server. To get around the CORS problem, I use Routing with a dispatch file:
https://cloud.google.com/appengine/docs/standard/python/how-requests-are-routed#routing_with_a_dispatch_file
Normally, when the UI server wants to call API server, it callsapi-dot-MY_PROJECT.appspot.com
In this workaround, the UI server calls itself with a specified path ("/api"):MY_PROJECT.appspot.com/api
Since the UI server is calling itself, CORS does not apply.
In the same GCP project I have two App Engine services:
- A UI server
- An API server
The UI server makes calls to the API server. To get around the CORS problem, I use Routing with a dispatch file:
Normally, when the UI server wants to call API server, it calls
In this workaround, the UI server calls itself with a specified path ("/api"):
Since the UI server is calling itself, CORS does not apply.
Description
Version used: 1.0.0-alpha3
Devices/Android versions reproduced on: Nexus 5X
- Sample project to trigger the issue.
Create 2 projetcs using same sharedUserId
make them to create RoomDatabase in same file location
use live data to observe changes
change data from application A and observe it on Application B
--Fail (can not be observed)--
- A screenrecord or screenshots showing the issue (if UI related).
N/A
This issue is not about sharedUserIds I get it. If you are using a database from SDcard and working on it with different applications, you will not be notified with changes on each application. LiveData on Room invalidates compute of changes with beginTransaction so if another application changes a table you observed, Room will not change in memory application database table, so second application will not be notified.
My suggestion to solve this issue is; create a valid, "not in memory" version table and create a hash instead of integer version_number for each table and track the changes on this hash.