🐛 Bug Report: Issue with Expo

[mi5ha]

👟 Reproduction steps

When installing react-native-appwrite in current Expo project (v52.0.28), there is a conflict with several package versions (metro, metro-resolver, metro-config)

To see an issue run:

npx expo-doctor

The reason this happens is because the way package.json is defined.

It sets both "dependencies" and "peerDependencies". Because "dependencies" are more restrictive this versioning issue happens.

Probably "dependencies" should be removed and just "peerDependencies" kept? That would solve versions issue I think.

👍 Expected behavior

Versions issues should not be reported.

👎 Actual Behavior

Expo doctor shows these issues:

Detailed check results:

Expected package metro@^0.81.0
Found invalid:
  metro@0.80.12
  (for more info, run: npm why metro)
Expected package metro-resolver@^0.81.0
Found invalid:
  metro-resolver@0.80.12
  (for more info, run: npm why metro-resolver)
Expected package metro-config@^0.81.0
Found invalid:
  metro-config@0.80.12
  (for more info, run: npm why metro-config)

🎲 Appwrite version

Version 0.7.x

💻 Operating system

MacOS

🧱 Your Environment

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[mi5ha]

As a temp solution putting this into package.json removes the doctor issues:

  "overrides": {
    "react-native-appwrite": {
      "react-native": "0.76.6",
      "expo-file-system": "^18.0.7"
    }
  }

[rparida1052]

This solution did not work

[mi5ha]

This solution did not work

Did you pair it with your versions of react-native and expo-file-system?

Btw its maybe better to add ^ for react-native also:

"react-native": "^0.76.6",

[rparida1052]

yes,sure

[viju-sharma]

As a temp solution putting this into package.json removes the doctor issues:

  "overrides": {
    "react-native-appwrite": {
      "react-native": "0.76.6",
      "expo-file-system": "^18.0.7"
    }
  }

Hey, It did not fix the issue, can you please help ?

[1stepdev]

Same problem here reported by expo doctor:

✖ Check that native modules use compatible support package versions for installed Expo SDK
Expected package metro@^0.81.0
  Found invalid:
    metro@0.80.12
    (for more info, run: npm why metro)
Expected package metro-resolver@^0.81.0
  Found invalid:
    metro-resolver@0.80.12
    (for more info, run: npm why metro-resolver)
  Expected package metro-config@^0.81.0
  Found invalid:
    metro-config@0.80.12
    (for more info, run: npm why metro-config)
  Advice: Upgrade dependencies that are using the invalid package versions.

npm ls metro show that:

├─┬ react-native-appwrite@0.7.0
│ └─┬ react-native@0.73.11
│   └─┬ @react-native/community-cli-plugin@0.73.18
│     ├─┬ metro-config@0.80.12
│     │ └── metro@0.80.12 deduped
│     └─┬ metro@0.80.12
│       └─┬ metro-transform-worker@0.80.12
│         └── metro@0.80.12 deduped
└─┬ react-native@0.76.7
  └─┬ @react-native/community-cli-plugin@0.76.7
    ├─┬ metro-config@0.81.1
    │ └── metro@0.81.1 deduped
    └─┬ metro@0.81.1
      └─┬ metro-transform-worker@0.81.1
        └── metro@0.81.1 deduped

What is the correct way to handle that ?
Can the react native appwrite sdk be updated to last version of react native ?

[ChiragAgg5k]

@mi5ha thanks for raising this issue. The team has noted the issue down and will release a fix soon 🙏

[ChiragAgg5k]

Closing as this should be fixed with latest release 0.7.2