flutterfire VS grpc-go

My react native app for some reason crashes every single time when signing out on iOS. The signout is successful, because I can see the page begin its transition to the home screen, and the next time I open the app, I'm logged out. I believe this is a firebase issue since it only occurs on iOS, and not on Android. I've looked at every related post I can find online, such as this one (Flutter) and this one (React Native) referencing active snapshot listeners, but even when I comment out my single snapshot listener, the crash persists.

I see. It looks like they’ve added support for it, see PR. You could give it a try.

Pushyy uses java classes from flutterfire firebase_messaging, which also has an iOS package. You could maybe build a wrapper similar to pushyy with it.

Sure, sure. You are special and ahead of Flutterfire issues: https://github.com/firebase/flutterfire/issues/10353

The ProfileScreen in this package has an option to use another provider when you are already authentified. https://github.com/firebase/flutterfire/blob/master/packages/firebase_ui_auth/lib/src/screens/profile_screen.dart

I don't know if you'd want a solution to this (considering no one asks for help in this sub due to the stupid Rule 2), you can read through this link - https://github.com/firebase/flutterfire/issues/7237

The package you've pointed to seems to be very new "Published 2 days ago" I would use the GitHub documentation (the learn more here link on Pub dev) on a fresh flutter project https://github.com/firebase/flutterfire/tree/master/packages/firebase_ui_auth/doc be sure to install the Firebase CLI (https://firebase.google.com/docs/cli#install_the_firebase_cli) as when you get to the configure part you'll receive

The lack of full native Dart support, slow build times, sketchy workarounds, and no desktop support led me searching for another solution. After many hours of research, I was faced with the choice between two frameworks: Appwrite and Supabase. Both were great frameworks and both fit my use case perfectly. But, I decided to move forward with Supabase because of their philosophy of “ not reinventing the wheel”.

For the moment, the pre-compiled SDK doesn't work with the latest flutter firebase libraries: https://github.com/firebase/flutterfire/issues/9761 So it takes an hour to build my project in GitHub action. I can't live with it!

The reflection service is open-sourced (at least for some sdks):

* https://github.com/grpc/grpc-go/blob/master/Documentation/se...

* https://chromium.googlesource.com/external/github.com/grpc/g...

We’re hoping to make this rate at least optional via this pull request but as the time of writing this blog, it’s nothing we can do to circle our way around it.

First, I started with gRPC’s recommended starter repository for learning gRPC, their **helloworld **example, which is a part of the official gRPC repository.

IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here

If you read the first comment, you’ll see the API was documented as being experimental.

https://github.com/grpc/grpc-go/issues/3798#issuecomment-670...

The lack of this analysis still results in bugs and CVEs. See how many races are found and fixed in gRPC releases: https://github.com/grpc/grpc-go/releases (search "race"). It's a shame Google does not publish these as CVEs, because many of them qualify.

I like to point people at this release to show that not even Google -- in its own language on its own library for its own RPC protocol -- can write thread-safe Go, so what chance does anyone else have. Maybe we have to stop thinking of Go as a language for mission critical parallel computing and think of it more like a Python 4 made for low-risk prototyping. Mature libraries help for that prototyping, you know how to put them together and get something working, that something just won't be scaleable, efficient, or thread-safe.

I first learned about this technique when gRPC generated code started using it. See the short readme and the long issue discussion. I think a lot more of the rationale from the discussion should have made it into the readme, since this is the only time most Go developers will ever see this technique used, especially since it can't be retrofitted to existing interfaces without breaking existing implementations.

I don't have any experience with goRPC (I'm assuming you're referring to https://github.com/valyala/gorpc), but just to note that that repo hasn't been updated in 7 years and has open issues that are that old, too. https://github.com/grpc/grpc-go has 17.5k stars and is actively maintained. That doesn't say anything about their relative performance - goRPC might be faster - but you probably won't have a fun time if you run into issues.

Found the root cause from https://github.com/grpc/grpc-go/commit/383b1143 (original issue: https://github.com/grpc/grpc-go/issues/75):

    // Note that ServeHTTP uses Go's HTTP/2 server implementation which is