mibto

Hello, I have exactly the same issue. It would be awesome if we somehow can continue to use angular with meteor.

it also works with angular 8... our current setup. i wanted to try out ivy

@cosmin-dumitrache can you please try it with version 0.3.4 - i have it working with AOT and angular 8.2.14 and meteor 1.9.2

@cosmin-dumitrache thank you very much for the better / proper fix. Do you also get following "error" when using meteor --production or meteor build: ``` meteor --production Warning: The --production...

I just found it - this happens when you redirect traffic from the container registry to the artefact registry. Unfortunately i already finalized the redirect. is there an other way...

Hi @dackers86 uff i have no idea who the right team would be for this issue. I can create the issue there, if someone can point me to the correct...

I just found the "solution" --> go to https://console.cloud.google.com/functions -> edit the functions -> expand "Runtime, build, connections and security settings", select "SECURITY AND IMAGE REPO", under "Image repository", select...

@pavelgj Sorry for the late answer. I get the following Error entry: "build": ERROR: failed to export: failed to write image to the following tags: [eu.gcr.io/workid-d9387/gcf/europe-west6/b31a43cd-0ef1-485e-8744-1a2516637136:ext-firestore-typesense-search-indexToTypesenseOnFirestoreWrite_version-1: GET https://eu.gcr.io/v2/token?scope=repository%3Aworkid-d9387%2Fgcf%2Feurope-west6%2Fb31a43cd-0ef1-485e-8744-1a2516637136%3Apush%2Cpull&scope=repository%3Agae-runtimes%2Fbuildpacks%2Fnodejs14%2Frun%3Apull&service=eu.gcr.io: DENIED: Permission...

``` "environmentVariables": { "DATABASE_INSTANCE": "", "DATABASE_URL": "", "EXT_INSTANCE_ID": "firestore-typesense-search-p78z", "FIREBASE_CONFIG": "{\"projectId\":\"workid-d9387\",\"databaseURL\":\"\",\"storageBucket\":\"workid-d9387.appspot.com\"}", "FIRESTORE_COLLECTION_PATH": "occupations", ``` this looks a bit suspicious to me empty database_url / instance

Hi @i14h I found the issue, it's because i redirected the traffic from container registry to artefact registry. i have reproduced it with a new project. unfortunately i already finalized...