You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I wondered why my callable functions not working anymore. Then I saw that you tell "Support region configuration via FunctionsRegionToken". But if you not set it, the region is "null" and this region not exists.
So at the moment it is required to add { provide: FunctionsRegionToken, useValue: 'us-central1' }, to the providers section. From my point of view everyone who uses AngularFireFunctionsModule and callable functions, this is a BREAKING CHANGE
My feature request
it would be better, if no RegionToken is set, that the default value is 'us-central1'.
The text was updated successfully, but these errors were encountered:
Sweet, this saved me some time.
I'm developing a Ionic3 app and was trying the new Functions module. Without the above solution the url started with 'https://null-' because the region info is missing.
Today I wondered why my callable functions not working anymore. Then I saw that you tell "Support region configuration via FunctionsRegionToken". But if you not set it, the region is "null" and this region not exists.
So at the moment it is required to add
{ provide: FunctionsRegionToken, useValue: 'us-central1' },
to the providers section. From my point of view everyone who uses AngularFireFunctionsModule and callable functions, this is a BREAKING CHANGEMy feature request
it would be better, if no RegionToken is set, that the default value is 'us-central1'.
The text was updated successfully, but these errors were encountered: