search

Greenstand / treetracker-wallet-app

The Greenstand Wallet App
https://wallet.treetracker.org
14 stars 43 forks source link

Add Bottom Navigation #268

Open pierrelstan opened 2 weeks ago

pierrelstan commented 2 weeks ago

Issue: Focused on the web Next.js app.

Description: create a bottom navigation bar for the home page. This navigation bar will contain buttons for easy access to the Home, Send, and Settings pages.

Hints: Please review the login and signup pages to see how similar components are structured and styled for consistency.

Design Reference: You can find the design and placement details in the Figma file here.

Note: Feel free to start working on this issue right away—you don’t need to wait to be assigned. The first completed pull request will be prioritized for review and considered for acceptance. If you have any questions or need help with design specifics, please reach out!

ImageImage

yuriBaza23 commented 2 weeks ago

Hi, I'm going to start working on this issue

Seiyaroo commented 2 weeks ago

Hi there @pierrelstan I was looking to get started and try to contribute but ran into some issues upon starting the project. I'm working on Windows OS, and get this error

image

I've tried both Android Studio version Ladybug 2024.2.1 Patch 1, and Webstorm 2024.2.4, and both get the same error found above even after running a clean install with Yarn install. I am likely doing something wrong, but wanted to check in and see if this is a bug with an upgrade to something internally version wise.

pierrelstan commented 2 weeks ago

Hi @Seiyaroo , try these steps to resolve the issue:

  1. Delete all node_modules folders from the root, web, native, and core directories.
  2. Delete the .expo folder from the native directory.
  3. Run yarn in the root directory to install all the packages.
  4. Run yarn start (native folder)

Feel free to reach out if you have any questions or if the issue persists.

Seiyaroo commented 2 weeks ago

@pierrelstan Looks like I still get this error after the above attempted fix.

image

I do have a blank page though

image

Is a blank page expected behavior at this point? I'd imagine there would be some basic scaffolding or templated thing out but not sure. Maybe I am seeing things correctly?

pierrelstan commented 2 weeks ago

@Seiyaroo Did you get the same error on the Android emulator? To clarify, we're not working on the web features in the Expo app (native); we're focused on the native side (android, iOS).

Seiyaroo commented 2 weeks ago

@pierrelstan Same result, blank page clean yarn run to install everything.

I'm at the following point in the structure when I run yarn start

image

pierrelstan commented 2 weeks ago

@Seiyaroo Could you share the error from the Android emulator? It would help me get a better idea of what’s going wrong.

pierrelstan commented 2 weeks ago

@Seiyaroo Try updating the main branch with the latest changes and follow the steps I suggested.

Seiyaroo commented 2 weeks ago

Sorry had to dinner @pierrelstan So this is in android studio

image

Fresh clean install of everything, even deleted the folder / clone and made sure to start fully fresh. Still get a blank white page. At this point I think it's me but I don't know enough to really say hah

pierrelstan commented 1 week ago

@Seiyaroo, Could you please sync your main branch with the latest changes from upstream/main?

Seiyaroo commented 1 week ago

@pierrelstan image

White screen once loaded via android studio. Error below is shown up in both Android Studio and Webstorm.

image

pierrelstan commented 1 week ago

@Seiyaroo Let's try one last attempt to resolve the issue:

  1. Delete all node_modules folders from the root, web, native, and core directories.
  2. Delete the .expo folder from the native directory.
  3. Run yarn in the root directory to install all the packages.
  4. Run yarn start (native folder).

If the issue persists, let's schedule a Slack meeting to troubleshoot further.

Seiyaroo commented 1 week ago

@pierrelstan Same issue unfortunately. Definitely would love to set up some time!

pierrelstan commented 1 week ago

@Seiyaroo, try again to update your main branch with the latest changes and then follow the steps I previously suggested.

Seiyaroo commented 1 week ago

Sorry it took so long. Busy weekend! @pierrelstan looks like whatever you did fixed it. So thank you for all your efforts!

image

Am seeing assuming expected behavior on the app now. Unfortunately it looks like someone referenced this PR so curious if it got fixed. Will look at the other newbie friendly ones and see if I can help out :D