-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java project error: cannot find symbol: OpenSourceMergedSoMapping #47633
Comments
Warning Missing reproducer: We could not detect a reproducible example in your issue report. Please provide either:
|
@ObscurusGrassator Can you re-try after cleaning all the caches ones?
|
@shubhamguptadream11 No, cleaning all the caches did not help. |
Same issue following https://react-native-community.github.io/upgrade-helper/?from=0.75.4&to=0.76.2 and still having a MainApplication.java instead of kt. I also cleaned everything. |
Same here. Followed https://reactnative.dev/blog/2024/10/23/release-0.76-new-architecture#breaking-changes-1 to upgrade to 0.76.2, and hit this too! |
Same here. If you're facing the problem it's worth converting just your The rest of your files, including
|
It worked successfully! Thank you. However, I'm really curious as to why Java couldn't find the symbol. |
In Don't forget to catch the |
Thanks @c100k , your solution doesn't throw an error, so I can close this issue. |
Description
I create new r.n. app (by last instruction) and transform kotlin files to java (Kotlin files working good).
(By the way, it is a huge fail that you have officially stopped supporting Java projects)
Steps to reproduce
I create new r.n. app (by last instruction) and transform kotlin files to java (Kotlin files working good).
(By the way, it is a huge fail that you have officially stopped supporting Java projects)
There is probably a problem with overwriting this file:
MainApplication.java:
React Native Version
0.76.2
Affected Platforms
Runtime - Android, Build - MacOS
Output of
npx react-native info
Stacktrace or Logs
Interesting: the import does not report a problem:
The text was updated successfully, but these errors were encountered: