Example application for React Native

[petertonysmith94]

Summary

Currently, we have no example applications that use React Native. The documentation, suggests to use Expo so we should follow their advice:

• Create a React Native application in our apps/* directory:

  npx create-expo-app@latest

• Add some simple functionality for testing purposes:

  • Create provider
  • Generate wallet
  • Check balance

• The following Signer logic has been reported to fail during build, it would be good to confirm:

import { Signer } from "@fuel-ts/account";
const extendedPublicKey = Signer.extendPublicKey(new Uint8Array(publicKey));

[danielbate]

This could be a contender for good first issue? We've got some similar apps and its isolated from src, could be good for someone with native experience to pick up.

[YaTut1901]

hello, I can take this

[petertonysmith94]

Go for it @YaTut1901 - as always, give me a shout if you need anything 😄

[YaTut1901]

@petertonysmith94 hello, regarding this task, I had several issues to build react-native with pnpm monorepo - unexpectedly that appeared to be not trivial. Now I can't resolve the problem that fuels package that is decalared with "workspace:*" can't be found when build with expo. Could you check if I miss something? The branch is here: https://github.com/YaTut1901/fuels-ts/tree/YaTut1901/feat/demo-react-native

[petertonysmith94]

@YaTut1901 I'll try give this a look over for you today, but it might be early next week :)

[YaTut1901]

@petertonysmith94 hello, have you managed to check it?

[petertonysmith94]

Hey @YaTut1901 👋🏼

I had a quick look, have you looked over the follow resource about managing a monorepo with Expo?

[YaTut1901]

@petertonysmith94 yes, I've done it accordingly with that page, but it can't build project properly. So I've done it using workaround from this issue: expo/expo#28775
Seems like working well unless it can't resolve fuels package while building. Strange thing that it can resolve it while compiling and VS code show no warnings regards that

[petertonysmith94]

@YaTut1901 I haven't had the time to properly look over your solution yet.

Potentially a better way forward, might be create a React Native app outside of our mono repo and getting that integrated with fuels successfully. That way, we can eliminate all the mono repo related issues (which I'm sure there are a few).

[YaTut1901]

@petertonysmith94 how do you suggest to do it? A separate repo?

[petertonysmith94]

@YaTut1901 Yeah a seperate repo would be ideal.