Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@melezorus34 Listen here, buddy, it's not some minor API version difference, it's a whole different API with a different name and endpoints, you'd fucking notice something's wrong if the documentation said to use "newApi.doNewStuff" and your code had "oldDeprecatedApi.doOldStuff". Also it's pretty fucking clear which one you're using when the error message says "Failed to authenticate to the new API - project not allowed".
-
What programming language are you using?
It's a shitstorm but I've managed to get it working correctly for me with both Js and Flutter projects. The documentation is not clear, they seem to miss out important parts but it usually boils down to whether you are using legacy http or http v1 api (also, I hate that naming convention. Why not V1 and V2??)
Related Rants
every single fuckening day
How documentation works
How the fuck is Firebase still a thing? I just spent hours debugging a random "not authorised" error, only to find out you need to enable a deprecated API even if you're only using the new (recommended) one. Do they tell you about it? Fuck no, they keep it disabled by default, they tell you to only use the new API, and they make it pretty much impossible to find the deprecated API you need to enable without a direct link.
And why the fuck does the official SDK send image URL as { "imageUrl": "http://..." }, when the endpoint expects it to be { "image": "http://..." }? Why the fuck does the documentation mention both options interchangeably, while only the latter one actually works?
rant
documentation
firebase
garbage