Mapbox navigation integration

While setting up the project, I encountered several issues that disrupted the workflow and kept recurring in a loop. First, the Gradle daemon lock issue prevented me from deleting the .gradle folder because it was locked by another process, showing the error “The process cannot access the file because it is being used by another process.” Next, there was a Kotlin version incompatibility, where the project expected Kotlin 1.6, but the Gradle plugins used Kotlin 1.8+, resulting in the error “Module was compiled with an incompatible version of Kotlin. Metadata is 1.8.0; expected 1.6.0.” As a temporary fix, I set kotlinVersion = "1.6.21" in build.gradle. I also ran into an unsupported class file major version 64 error because I was using Java 20, which was too new for Gradle. This was fixed by installing Java 17 and pointing org.gradle.java.home in gradle.properties to the correct JDK path. Additionally, dependency resolution failed for components like manifest-merger and zipflinger, throwing 404 errors due to broken URLs or improperly configured Maven repositories. Another issue was the missing React Native Gradle plugin, where the error “Plugin with id 'com.facebook.react.rootproject' not found” appeared, caused by an incomplete React Native setup. Finally, I noticed the react-native folder was missing in node_modules, which resulted in the error “Could not read script 'node_modules/react-native/react.gradle' as it does not exist”, likely because npm install or yarn install hadn’t completed successfully earlier. These issues combined highlight the need to carefully align Java, Kotlin, and Gradle versions, ensure proper dependency resolution, and confirm React Native is fully installed in the project. Unfortunately, these errors keep appearing in a loop, making it challenging to move forward.