RocketChat / RocketChat/Rocket.Chat.ReactNative

Post node, npm, yarn, XCode and Android Studio versions of the official app in README

Open
#3,070 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🍭 good first issue 📝 docs
Dominant language
TypeScript
Stars
2.4k
Forks
1.5k
Avg merge
1d 18h
Merged PRs (30d)
90

Description

Description:

After finding out that my issue #3009 was a regression obviously caused by a different node version when buildung my app, I'd highly appreciate if the team would make a note with which version of

  • node
  • npm
  • yarn
  • XCode
  • Android Studio

the official app is currently built. This can be either in the README here in the Github project or in the whitelabeling docs, but it should always kept up to date to avoid such issues.

Environment Information:

Don't care

Additional context:

Background story:

In my IOS app, as mentioned in #3009 the icon badge number was not cleared by closing the app after the messages have been read, so the icon always showed unread messages which leads the users to not recognize new messages.

This was introduced with 4.15.0, but I was wondering that neither the official RC app not the RC experimental app in Testflight showed this issue.

After I've updated node from 14.15.0 to 15.14.0, npm from 7.7.6 to 7.9.0 and having my app recompiled the issue was gone.

If we could keep our versions par with the versions the official apps are compiled with, these kind of issues could be avoided.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Update the project README or whitelabeling documentation with the Node, npm, Yarn, Xcode, and Android Studio versions used to build the official app. First inspect the current README and related documentation, then verify the official build versions and ensure the published list is clear and maintainable.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, react-native
Domain
documentation, mobile
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.