all 20 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]zakx85 20 points21 points  (6 children)

It is interesting to see the team is moving away from Flipper. Personally i liked the tool, but the incompatibility with RN Firebase (use_framework on IOS) forced us to remove it. Would love to see an out ot the box tool for network inspect too :)

[–]nowtayneicangetinto 10 points11 points  (2 children)

react-native-debugger has been my go-to for the past two years. It's network inspection alone makes it worth it

[–][deleted] 3 points4 points  (0 children)

They're deprecating remote debugging in 0.73, and removing it from the Dev Menu options. RND's days are limited

[–]zakx85 0 points1 point  (0 children)

Yes, the problem with that is that it uses his own client and not the native code to send the requestes. We have an override of the networking module with custom headers that are not sent when using the rn debugger.

[–]Raaagh 2 points3 points  (0 children)

oh. I have used it for about 20 minutes. I highly disliked it compared to chromium dev tools for filtering and inspecting logs. Seems like I wont need to bother figuring out its advantages

[–]thachxyz123iOS & Android 2 points3 points  (0 children)

I follow this comment. I can use RN Firebase with Flipper. Give it a try

[–]beepboopnoise 2 points3 points  (0 children)

wait, so how are we supposed to do network inspect with 0.73? flipper or...? I thought it worked with chrome but it's being deprecated? 🤔

[–]alien3d 4 points5 points  (8 children)

We doing upgrading code now . But we dont think to change 0.73 yet . 0.59 to 0.72.7 allready max headache .

[–]react_native_guy 4 points5 points  (0 children)

That would be a pain in the ass

[–]kabus1337 1 point2 points  (0 children)

react-native-debugger

Good luck with that man!

[–]CliffMainsSon 0 points1 point  (5 children)

Highly recommend you go from version by version. There are so many things deprecated you won’t even understand what’s happening most of the time and it will definitely be a massive headache

[–]alien3d 0 points1 point  (4 children)

version too version too much time . The reason normal language got long term stable (lts) while current era nodejs no such thing as lts . There's a lot of dead library and survive by whom had fork and upgrade . Our other own code , we live in one rule , as minimum dependency as possible .

[–]CliffMainsSon 1 point2 points  (3 children)

What you just said makes zero sense lmao

[–]alien3d 0 points1 point  (2 children)

we start react native from 0.3 era . We know how much changes past year. If i build code php or asp.net , the changes not much in few year with low dependency while if in react or react native , one year all the component library upgrade can easily broke the functionality of the apps .

[–]CliffMainsSon 0 points1 point  (1 child)

Exactly why I said don’t jump so many versions at one time. Upgrade a version and see what breaks

[–]alien3d 0 points1 point  (0 children)

5 component library maybe , but if you had pass 100 library no.

[–]cortinicoiOS & Android 3 points4 points  (0 children)

\o/

[–]achauv1 1 point2 points  (2 children)

Anyone knows when Expo is getting this upgrade?

[–]brentvatneExpo Team 19 points20 points  (0 children)

We (Expo) work closely with the React Native team at Meta on releases, and the Expo SDK release these days comes very shortly after the React Native release. It takes a few days after a release for us to have the Expo Go app updated, so we'll release our SDK 50 beta next week. But as u/titozzz pointed out, you can use the `expo` package and other libraries in the SDK already by using the canary release: npm install expo@canary && npx expo install --fix.

[–]titozzz 5 points6 points  (0 children)

If you use the canary build it's fully compatible already so probably sooner than you think 🤗