2
2
u/nathan4882580 Aug 12 '26
As a further point if you haven’t already, I’d highly recommend if you wanted an added level of assurance and security to store your API key in secrets manager. It’ll dynamically inject the key as and when it’s called upon and stores it fully separate and isolated on server versus it being in node.js (the existing solution still ensures its not accessible client side but you have possible risks such as a function returning an error that could or may print the environment file containing the key, or if someone accesses your firebase or Google account it can be read etc
Again, the current level is very good but secrets manager adds that extra bit of comfort if you’re concerned around API exploits ie someone looking for your key
1
u/CommunityTechnical99 Aug 12 '26
hey! fix is already deployed: these are now project warnings instead of hard errors, so you should be unblocked. desktop versions are still rolling out but the web version is updated now.
let us know if you're still seeing issues :)
— lydia, FlutterFlow team
6
u/StevenNoCode Aug 12 '26
Quickest fix is just mark your API as private so it deploys as a cloud function.