Redundant Language Settings Issue in Enatega Multivendor Rider App for iOS

Open

#1,744 opened on Jul 6, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 50/100

Issue type: Refactor
Clarity: Mostly clear
Activity status: Quiet
Tech stack: ios, javascript, react-native
Domain: internationalization, mobile

Research direction

The issue mentions the Rider app’s in-app language settings and iOS device defaults, but no file or test. Start by locating the language-settings entry point and related iOS localization handling; confirm that the app follows the device language after closing and reopening.

Written by the indexing model from the issue text.

Description

Summary:
The Enatega Multivendor Rider App for iOS currently includes its own language settings, which are redundant given that iOS devices already have default language settings.

Steps to Reproduce:
Install the Enatega Multivendor Rider App on an iOS device.
Observe that the app initially relies on the default language settings of the iOS device.
Navigate to the language settings within the Enatega Multivendor Rider App.
Change the language settings within the app to a language different from the default language of the iOS device.
Close and reopen the app.
Notice that the app now has conflicting language settings, resulting in a redundant language interface.

Expected Behavior:
The Enatega Multivendor Rider App should seamlessly integrate with the default language settings of iOS devices. Users should not need to configure language settings within the app separately.

Actual Behavior:
The app has redundant language settings, causing confusion for users. The language settings within the app conflict with the default language settings on iOS devices, introducing unnecessary complexity.

WhatsApp.Video.2023-12-07.at.12.00.47_667b254f.mp4

Dominant language: JavaScript
Stars: 0
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

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