React Native with Firebase - Has it a future?

[Matthias Kühnle]

My question is not technical. More about the Roadmap.

Firebase 3.0 is incompatible with React Native und the solution is to use a 2.x Version of the SDK.

But can anyone from Google/the Firebase Team say a word of the future? Do you plan to fix that/was that a incident? Or was it accepted because the RN userbase was/is to small?

Is there a future for React Native and Firebase? Or is it better to now switch / prepare for a switch - maybe to horizon? 

Thanks & and it is ok to say "better look somewhere else, RN is not on our Roadmap yet" - I just like to know...

cheers,

Matthias

[Kato Richardson]

Hi Matthias,

There has been several posts about React Native on the list. This Stack Overflow may be the most informative. React Native is not a supported framework yet, but we've helped out where we can.

It's on our radar but not yet on our "road map" per se. That could change at any time, particularly as RN matures and grows in adoption. React and RN have a lot of advocates on the team and someone may champion this. For the present, I think it's up to the community to initiate this effort.

I hope that helps!

☼, Kato

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/29b21b6f-fe93-4052-9f72-c7597632c17a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Kato Richardson |

Developer Programs Eng |

kato...@google.com |

775-235-8398

[Daniel Steigerwald]

Did anyone test whether Firebase Web JS version works in RN?

[Chetstone]

Hi Kato,

It's news to me that React-native is not a supported platform. My app has been working fine with firebase 2 on RN for over 6 months, thanks to helpful support I have received on this list from the firebase team.

I'm curious about what is new in 3.0 that necessitates the regressive dependence on "document " that broke compatibility.

@Kato when you say it's up to the community to initiate the effort, what do you suggest we can do? AFAIK firebase is not open source, or did I miss something?

Also, if there is a stackoverflow question with more details on this, I wonder if you would mind posting a link?

Thanks

Chester Wood

[Kato Richardson]

I believe this stack overflow question is the one I intended to link to. We don't test against RN for release certification, so there's always the chance of breaks like this. But I'm happy to help troubleshoot and find workarounds.

The simplest answer, and the part where the community can initiate the effort, is to find out how things are breaking (both RN and Firebase are growing fast, and not necessarily in parallel) and to keep letting us know, as well as helping us keep track of which versions are stable for use with RN, until we have a better support story.

For now, 2.4.2 seems like the best version.

☼, Kato

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/affb7a1b-1787-4467-a1f6-8aef39f4d460%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Deep Ganatra]

So basically, we migrate the app from dashboard or use the old SDK?

Or we don't migrate at all and use deprecated version? (If this is the case, how long will the old version work?)

[Kato Richardson]

We have yet to deprecate any of our API versions, all the way back to 1.0. They still run. The 2.x versions are also not deprecated. Continue to use them.

The only thing deprecated is the old app dashboard/console (firebase.com/account). We've migrated that to https://console.firebase.google.com and added a new billing system into the mix. You should migrate to the new console soon.

On Tue, May 24, 2016 at 9:59 PM, Deep Ganatra <de...@web1.in> wrote:

So basically, we migrate the app from dashboard or use the old SDK?

Or we don't migrate at all and use deprecated version? (If this is the case, how long will the old version work?)

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/64d60ffa-fcad-48aa-992b-db9b5cfb82b7%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Jacob Wenger]

Note that we cannot say this enough: you can migrate to the new console and still use the old 2.x.x SDKs. We encourage you to do that if you are blocked upgrading to the 3.x.x SDKs for whatever reason.

Jacob

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CADypTEbE1mLELvedZW9QLMa4fsHYbe7M%2Bw2W2Co7-N8QmEg6Kg%40mail.gmail.com.

[Chester Wood]

On Tue, May 24, 2016 at 12:46 PM, 'Kato Richardson' via Firebase Google Group <fireba...@googlegroups.com> wrote:

The simplest answer, and the part where the community can initiate the effort, is to find out how things are breaking (both RN and Firebase are growing fast, and not necessarily in parallel) and to keep letting us know, as well as helping us keep track of which versions are stable for use with RN, until we have a better support story.

So the community has let you know that RN is broken for FB 3. The community is not going to be able to any further testing until the dependence on document  is removed. How will you communicate to the community when/if this issue has been addressed so we can do further testing?

BTW perhaps you could inform your JS developers that they could remove that dependence by testing for the react-native environment. 

The test for (navigator.product === 'ReactNative')  on the device has been in RN since 0.17, but unfortunately that doesn't help in the RN developer's debugging environment because "Gecko" is returned when debugging in Chrome. This is OK for performance enhancements but would probably not work in this case. 

For this you would use a custom entry point for React-Native in the firebase package.json. Support for this has been in RN since v0.17 also. Of course, this is only necessary if the dependency on document cannot just be removed.

Thanks,

Chester

[Jacob Wenger]

Thanks for the feedback and info, Chester. We will make sure to post here and on other threads once we have something to say about React Native support. This is definitely on many people's radar (including mine), but we also have had a deluge of feedback and are trying to sort through everything still. We appreciate your patience while we do that.

In the meantime, please just stick with the 2.x.x SDKs for React Native. You can still migrate your project to the new console and use the old 2.x.x SDKs.

Cheers,

Jacob

--

You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAFj_e_dYgLcP_a84ooJAvB2Bn1BkmuPeAA53LN0Dc8v51jRvmQ%40mail.gmail.com.

[Matthias Kühnle]

Thanks Jacob & Kayo for the clarification of the status quo. 

[Matthias Kühnle]

The 2.4-SDK works fine with RN. But I can't get auth configured for apps that I created in the new console. Is there any hidden flag that needs to be enabled?

The same code&settings work for Projects that I imported from the legacy console. But for new Projects from the new Console the server response is always "Error: The specified authentication provider is not enabled for this Firebase". (It is configured and yes I turned it off and on again ;-D

So workaround for me so far: Always create new Projects in the legacy console and than import them into the new - but there should be a hint somewhere for the ReactNative-Folks. 

A "How to do ReactNative with Firebase3" with all the workarounds and hints would be nice....

[tomas...@happypancake.com]

We've just started 2 payed accounts (before the 3.0 and google cloud launch) and the use-case is only react-native for our part.

So for our sake and your probably it would make total sense to split dependencies so we can continue use the service in the future without missing out functionality.

Thanks

Tomas

[Matthias Kühnle]

Hi,

Important Note for all React Native Users and people that stuck with "Error: The specified authentication provider is not enabled for this Firebase”"

I just learned from the support: Projects that got created in the new FB-Console won't work with the SDK 2.x Auth-Methodes! You must create your new React-Native-Projekts in the old Console and than import them into the new Console. Only then the Auth-Methods from the 2.x-SDK work.

Not sure how long that is possible - but it works for now. 

cheers,

Matthias

[Atif Mansoor]

Thanks for the replies Jacob and Kato.
  I would like to suggest an alternative approach to thinking about this issue.  The reason that FBase3 JavaScript is not working in RN is because of it's reliance on client-side JS (document/window, etc.)   What we need to do is approach using FBase3 in RN from a server-side JS standpoint.  FBase3 supports C++, so it isn't far-fetched for Firebase to allow better support for server-side JS.  What that means is allowing devs to create users (and the other use cases) in addition to verifying tokens with server-side JS.

An even better approach is to have the API become completely RESTful so that we can use any language server-side.  I see this with other BaaS providers, how possible is this for Firebase?

Btw, fwiw, I tried using the nodejs Server SDK from within my RN app (to verify a custom token), but I got an error saying my apiKey was invalid.  I'm not sure if this is related to an error on my part or due to an incompatibility with RN.

I will in the meantime continue using version 2.4.2.  I may also investigate embedding native Android modules (which will use the Firebase android SDK) into RN.  There is someone working on that for iOS: https://github.com/holmesal/react-native-firebase

Thanks,
Atif

[Danijel -]

Disappointing that this problem has been thrown to the community to sort out. Especially since the source is closed!

Is it not possible to have the auth module support RN but with the explicit exclusion of the visual login screens?

For instance, in my use case I'm attempting to use 3x without using the Firebase login screens/flow. I've instead decided to build my own email/pwd and facebook screens (the later using https://github.com/facebook/react-native-fbsdk) and link those screens to Firebase using the auth api (i.e. using firebase.auth().createUserWithEmailAndPassword and firebase.auth().signInWithCredential respectively). 

@kato @jacob would the above compromise solution sidestep the issue preventing compatibility? 

Note: Someone presented a potential solution...http://stackoverflow.com/a/37577465/4497941. I'm going to try this out later to see if it supports the aforementioned workflow. 

Thanks 

[Jacob Wenger]

@Danijel - We are working internally on the problem. We are mainly looking for feedback from the community and I'm glad you are providing it. We don't have anything definitive to say on the topic just yet, but we are investigate how much work it would take to get things compatible with React Native again. Please hang tight and use the 2.x.x SDK until then.

@Atif - I'm honestly not sure what you are proposing. It's unclear to me how server-side JS, C++, and React Native are all related and what action item we would take to resolve the three. Also, Firebase does have a REST API for the realtime database, just not for auth. Lastly, you talk about using the verifyIdToken() method in your React Native app, but that method requires a service account and is intended for a trusted server, not an untrusted client. So, I'm a little lost as to what you are suggesting.

--

You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/177006e2-51ea-4e56-a4a7-6fbf588b7982%40googlegroups.com.

[Terry Liu]

It is rather unfortunate that the support for React Native (RN) dropped off on this release especially since it seemed to pair nicely up to v2.4.2. I was personally really looking forward to Firebase now that Parse has lost its core hosting support, but am now sad once again since it is not ready to play along with RN.

Having said that, I imagine the migration from Firebase 2.4.2 to 3.0+ won't be all that bad if support for RN gets officially added to the road map, so I just have few questions in the meantime:

1) It looks like the legacy Firebase API documentation (2.4.2 and below) is marked as being "DEPRECATED AS OF MAY 18, 2016" (https://www.firebase.com/docs/web/api/). Does that just mean the documentation itself will no longer be updated but the SDK methods will continue to function?

2) I saw it suggested that we can continue to use SDK 2.4.2 with the new Firebase console. However, I don't see my users being created under the auth section of the new console, and yet my app is telling me that users by those email addresses are already being used when I make calls to the old `firebase.createUser`. Am I missing something or will the old auth methods not work with the new console?

3) If the new Firebase auth will not work with RN, how long do we have until the old console is fully deprecated and no longer functional?

Thanks,

Terry

[Danijel -]

Thanks Jacob.

FYI, I tried http://stackoverflow.com/a/37577465/4497941 however I wasn't able to load the app using firebase.initializeApp(config); The app complains that 'Browser is not supported'. 

Not sure what else to try 

[Pier Bover]

Hey Jacob

I think the best solution for React Native would be as follows.

You already have SDKs for mobile (Java and Android). React Native supports native modules. You only need to build a bridge between the JS and the native code.

https://facebook.github.io/react-native/docs/native-modules-ios.html

https://facebook.github.io/react-native/docs/native-modules-android.html#content

As you can see from the docs it would be trivial to implement and maintain such modules for an organisation like yours.

Plus we'd get real data persistence on React Native which is not possible with the JS SDK.

[Daniel Steigerwald]

What is really scary, that bug seems to be trivial, but Google Firebase silence is sinister. I think they don't want to open source it, because quality of code. I have no other explanation.

You received this message because you are subscribed to a topic in the Google Groups "Firebase Google Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebase-talk/fvpjeYEg8L8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebase-tal...@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/fe14435f-b167-4bf1-81d8-78eb35ba6d72%40googlegroups.com.

[Pier Bover]

Hey Danijel

You need to do app.initializeApp(config)

For the database: database().ref(...)

This is when using the imports from the StackOverflow example.

--
You received this message because you are subscribed to a topic in the Google Groups "Firebase Google Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebase-talk/fvpjeYEg8L8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebase-tal...@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/fe14435f-b167-4bf1-81d8-78eb35ba6d72%40googlegroups.com.

[Atif Mansoor]

@Jacob The action item I was suggesting would be to have an API for creating users with server-side JS (for a nodeJs project for example) just like we can with C++. However, I didn't consider that although React Native uses node/server-side JS, it's still running on a mobile client, so it wouldn't make sense to treat it like a trusted server (like you do with C++).

If that's the case, then expanding the REST API for Auth makes the most sense (if you can't get the FBase3 JS compatible with ReactNative).  This is also a sort of future-proofing, for when the next ProjectXYZ (backed by SomeBigTechCompany) gets really popular in the streets, you won't have to build in specific compatibility with that project.
I would imagine that using the REST api for Auth may be more complex and involved, but that's a trade-off I would be willing to accept if it means getting it to work in my project.

Finally, I would suggest that Firebase put some notes/FAQ regarding this in the migration guide.  Something along the lines of this:
1. FBase3 does not support React-Native at this time; we are looking into it.
2. Please use FBase 2.x until then.

3. In order to use FBase 2.x, you will need to create a project in the legacy console, and then import it into the new console.  It won't work if you create a project in the new console.

4. Although FBase 2.x is deprecated, it still works for the time-being while we figure stuff out (heck, even 1.0 does).  So chillax.

Thanks,

Atif

[Pier Bover]

Yeah, their silence is what's really bothering me.

I have convinced a client to move everything to Firebase. And now I find I can't use Firebase with React Native.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAHJ5dLqaGzC_4kuDYb_xiWvg7bnYi9WKyEry_S4OucDv%3DCx_cA%40mail.gmail.com.

[Danijel -]

Hi Pier,

Yeah i did. Did it work for you?

[Pier Bover]

Hey Danijel

Yes it did work. At least for the database... haven't tried other services.

You can read more about the versions I used here:

https://github.com/facebook/react-native/issues/7864

On Thu, Jun 2, 2016 at 5:31 PM, Danijel - <dan.ba...@gmail.com> wrote:

Hi Pier,

Yeah i did. Did it work for you?

--
You received this message because you are subscribed to a topic in the Google Groups "Firebase Google Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebase-talk/fvpjeYEg8L8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/69a2f57b-a658-4bea-b494-de60791eb31e%40googlegroups.com.

[Terry Liu]

Update: turns out the "Auth" portion of the new console does continue to work with the legacy API. I think there were issues with the Firebase authentication service in general when I was last trying, which is why it did not appear to work at the time.

Can anyone confirm whether the legacy API and console will be around for some time? How long?

TIA

[Sean]

Hi Kato I'm glad it's on the radar but it's apparent from these comments alone this is an important feature for a lot of people. 

I have just suggested the use of FB to many clients who use React-Native. I think React-Native Clients deserve a little more than the uncertainty that someone "may" champion this since offical Firebase React-Native documentation exists which I'm sure many people bought into this service thinking this would be supported. Any advise or to whom I should contact to voice my opinion on this would be greatly appreciated.

Sean.

On Wednesday, May 25, 2016 at 2:47:45 AM UTC+10, Kato Richardson wrote:

Hi Matthias,

There has been several posts about React Native on the list. This Stack Overflow may be the most informative. React Native is not a supported framework yet, but we've helped out where we can.

It's on our radar but not yet on our "road map" per se. That could change at any time, particularly as RN matures and grows in adoption. React and RN have a lot of advocates on the team and someone may champion this. For the present, I think it's up to the community to initiate this effort.

I hope that helps!

☼, Kato

On Tue, May 24, 2016 at 1:17 AM, Matthias Kühnle <mwie...@online.de> wrote:

My question is not technical. More about the Roadmap.

Firebase 3.0 is incompatible with React Native und the solution is to use a 2.x Version of the SDK.

But can anyone from Google/the Firebase Team say a word of the future? Do you plan to fix that/was that a incident? Or was it accepted because the RN userbase was/is to small?

Is there a future for React Native and Firebase? Or is it better to now switch / prepare for a switch - maybe to horizon? 

Thanks & and it is ok to say "better look somewhere else, RN is not on our Roadmap yet" - I just like to know...

cheers,

Matthias

--

You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/29b21b6f-fe93-4052-9f72-c7597632c17a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Jacob Wenger]

Hey all, I just wanted to give a status update on things here. Thanks everyone for their enthusiastic responses and suggestions for React Native support. We are working on bringing back React Native support to the 3.x.x JavaScript SDK. It is not a simple process as many new underlying dependencies were not designed with React Native in mind. I can't give you any definitive dates as we are still investigating and working through the open issues.

There was also some mention on creating a native adapter so that the Firebase Android and iOS SDKs can communicated with React Native. We don't have any plans to do this right now as far as I am aware. But this is definitely a great option and something we'd love to see from the community. I've actually got an email from a Firebase user in my inbox which is their attempt at this very thing. I'll make sure to share it if it materializes.

If React Native support is a blocker for you, please continue to use the 2.x.x SDKs until we resolve this issue. The 2.x.x SDKs will continue to work, even after you migrate to the new console.

As other people have mentioned in this thread and elsewhere, if you want to use React Native in a newly created Firebase project, you should create it from firebase.com/account instead of the new console.firebase.google.com console.

Thanks everybody for their patience,

Jacob

[Danijel -]

Woo! That's great news. The two technologies are such an excellent pairing. Thanks again :)

[Atif Mansoor]

That's great news, Jacob!  I'm very appreciative of this decision and your timely response.  I'm happy to know that Firebase listens to customer feedback.

[Pier Bover]

Hey Jacob

Thanks a lot for the response.

While fixing the JS SDK would be great, it would not solve the offline persistence problem.

It would be awesome if we could pool resources from the community to get the native adapter done. I will make a bit of noise in Slack, Medium and Twitter and see what happens.

Let's do this!

--
You received this message because you are subscribed to a topic in the Google Groups "Firebase Google Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebase-talk/fvpjeYEg8L8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebase-tal...@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/3e0efcf1-0158-4e39-86fe-3a518d016c5c%40googlegroups.com.

[Daniel Steigerwald]

If Google would open source a new client, I could help you because I have spent years wringing JS in Google Closure.
Now I can only guess. There is no such thing like React Native special environment. Just no browser. Except this one liner I am fine
https://github.com/johanneslumpe/react-native-browser-polyfill having it in Este.

[Chetstone]

For what it's worth, I vote for the JS client. It has been working great, and hopefully a few minor fixes will get it working again. 

I think an iOS bridge-based client would be certainly a good alternative, and I am glad Firebase is willing to support the RN community in building it, but I hope it won't detract from their efforts to fix the JS client.

I'm not sure if everyone understands that iOS client offline persistence is not complete: it doesn't support transactions, for example. My app uses transactions, so I had to build my own offline persistence, and I am worried about how well my implementation would work with an iOS-bridge client.

Building an iOS bridge is evidently hard, several people have tried, and although it is no doubt doable, I expect it will take months for a stable implementation to emerge.

In the meantime, I am looking forward to trying the new FB 3.0 auth features in the JS client in the near future.

Thanks,

Chester

[Benn Sandoval]

Hi Jacob,

I'm trying to use 2.x.x SDK with the new a project created with the new console and authentication is not working, I get "The specified authentication provider is not enabled for this Firebase" and I have the configuration of Google OAuth in place, in the same way of the older project in the previous console... Is there any workaround for this issue? or Should I continue using the previous console and app? 

On Thursday, June 9, 2016 at 3:58:58 PM UTC-5, Jacob Wenger wrote:

[Jacob Wenger]

Re-posting what I said at the end of my last message:

As other people have mentioned in this thread and elsewhere, if you want to use React Native in a newly created Firebase project, you should create it from firebase.com/account instead of the new console.firebase.google.com console.

​You can migrate it to the new console after enabling the providers you want to use.​

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/4ac06e3b-99e9-453a-a3d6-d3cf9c1e8d9b%40googlegroups.com.

[Antoine Rousseau]

Hi Jacob,

I tried creating a legacy Firebase account using firebase.com/account, without luck.

I followed the instructions which forced me to create a Google account (because my main one is already registered at firebase.google.com), which I did, but I get redirected to console.firebase.google.com after logging in anyway...

I'd love to be able to use Firebase in my React Native app, but I can't find any way of doing so.

[Jacob Wenger]

Hey Antoine,

As of last week, new signups are not allowed on firebase.com. You can only create legacy projects if you already have a legacy account. Thankfully, we should have tangible updates on React Native support very very soon. Hang tight!

Cheers,

Jacob

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/9ce40a82-fcfb-43dc-85e3-7c7cf4264ebd%40googlegroups.com.

[Antoine Rousseau]

Thanks Jacob, sounds good!

I think building a bridge is the only viable option, and I'm sure the community will be very active into helping your team to improve it if you release it on Github!

At least for the auth!

You received this message because you are subscribed to a topic in the Google Groups "Firebase Google Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebase-talk/fvpjeYEg8L8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebase-tal...@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAGcMwsDh6GYk3b%2BxNov2C%3Djg0J2Z_cnGiOcxoV7DJUx9SE-YCg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

—

Antoine Rousseau • Web R&D engineer

http://antoine.rousseau.im

[niztal]

Hi Antonie,

I already built this kind of bridge, you can see it in GitHub  - https://github.com/niztal/react-native-firebase-adapter

Please read the README.md file it describes all I've done and I'd really appriciate for some comments/pull requests.

Thanks,

Nitzan.

[Pier Bover]

In my current project, I'm more interested in real offline persistence for React Native apps. So when an offline user, closes and opens the app, the data remains there.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CANHEEm5GJqK4TZdn%2Bbq4hnYFt%3D-Eg%2BArovsWv%3DNA%3DYYuAcWkgA%40mail.gmail.com.

[Antoine Rousseau]

Wow, thanks Nitzan!

I'll try this method next week.

It'd be great if it could be an installable module using rnpm (never made one but I'll try if I can find time).

About your last paragraph in README ("I can tell honestly it's a workaround, and I think the firebase team should make for us the React-Native community a JS working SDK"), do you believe there cannot be any gain (performance, features) having a native bridge over using a full JS api?

Thanks again, and thanks community, you are awesome.

Antoine

--

You received this message because you are subscribed to a topic in the Google Groups "Firebase Google Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebase-talk/fvpjeYEg8L8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/c1bd8c06-f9d7-4a29-979d-d18430b00e72%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[niztal]

These are exactly the reasons why I've made thi module public and also communicated directly to the firebase team, so people could examine it and tell whether there are any performance/security issues. I personally don't have the knowledge nor the tools to tell so but I believe for the good of all of us that the community and the firebase team know and should answer these questions.
Thanks for the suggestion regarding the rnpm I don't have the time to do so it will be great if you take it.. thanks anyway.

[Pier Bover]

Hey Antoine

About your last paragraph in README ("I can tell honestly it's a workaround, and I think the firebase team should make for us the React-Native community a JS working SDK"), do you believe there cannot be any gain (performance, features) having a native bridge over using a full JS api?

Performance gains would be nice of course, but IMO the big advantage of the native bridge would be real data persistence.

The general JS SDK does not (and cannot) offer real data persistence. It can maintain some persistence during the current session if the connection goes off and comes back later, but if you close the RN app or the browser tab the data that wasn't synced with Firebase will be lost.

This data persistence situation can be solved by the famous native bridge, since AFAIK the Android and iOS SDKs do offer persistence at the native level, but the Jacob from the FB team has already said they won't be implementing it:

We don't have any plans to do this right now as far as I am aware. But this is definitely a great option and something we'd love to see from the community.

So, hopefully the auth problem that prevents the JS SDK to work with RN will be solved very soon (I have a demo in a week! :S) but we will still miss offline data persistence.

Another solution is to use Realm or RN AsyncStorage to create a data cache with persistence and some logic that uploads data to FB once the connection is reestablished. It's not as clean as the native bridge but it may be easier to implement and distribute as an NPM package.

I agree with Nitzan. I think the Firebase team should be implementing a custom tailored solution for RN like Realm has done.

In the following years RN is going to be a major tech in the mobile dev landscape for the simple reason that you can share a big chunk of your codebase among all your clients when using React and React Native: web, mobile, desktop (using Electron), and Chrome OS. That's the future.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CANHEEm7XxRGyVsT9WNNUjn8cWT%2BdnHQBLLUcdXynwutLRfMZ-Q%40mail.gmail.com.

[Jacob Wenger]

Version 3.1.0 of the JavaScript SDK was just released and it is now compatible with React Native. Read more about the release here.

--

You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAHhNJbJHO68SnFUNZ9rC_8i%2B%3DcmR4xNdeG0mxpVFSSiSiGNPxg%40mail.gmail.com.

[Antoine Rousseau]

Awesome, thanks!

Will try it asap :)

Best regards to the Firebase team.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAGcMwsD8xaqWryiUBEFc2c0gt3g1xrS%2B7P2uRPG2am%2BN1DG2kQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Antoine Ansel]

Hey,

I'm currently developing a React Native application with Firebase 3. I'm using the latest SDK (3.1.0) and it's working fine, great job!

I was very interested in Firebase because of its offline capabilities. The Android SDK seems to provide true offline capabilities with disk storage so it survives app restarts : https://firebase.google.com/docs/database/android/offline-capabilities#section-disk-persistence

I was hoping to have such functionality with React Native. Is that currently possible with the Javascript Firebase SDK? If not, is there a plan to implement this in the future?

Thanks!

Antoine

[Pier Bover]

Hey Antoine

The Javascript SDK doesn't offer offline disk persistence.

If you check the previous messages this has been discussed at length.

Regards

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/31b1b46e-7c91-461c-ba4e-58685fdff6f3%40googlegroups.com.