Aleksandar 'Alex' Gotev
Aleksandar 'Alex' Gotev
@kzaher if that is your scenario, then I agree with you is a serious security risk. One way I managed to resolve this is letting only the CI create releases....
@sraka1 I think the problem has to be inspected at RN bridge level, because the service works successfully in production on all Androids and no errors like this ever happened....
In native Android it doesn't make difference, but I don't know if in RN the two are treated differently.
You don't need to add any service declaration in your manifest. Just follow the getting started wiki page and make sure you set your package ID correctly by following the...
In normal conditions in a fully native app, if you don't configure the namespace correctly it simply won't start and the solution is in the getting started wiki. Post the...
The last thing you should try is the upload service demo app with your same settings. I bet that null is because of something done by RN unless proven otherwise.
If RN is not merging manifests, it can be a problem. Nowadays all the libraries on Android rely on the Gradle manifest merger to avoid having to mess around with...
On native Android even multiple nested project's manifests are merged by Gradle without problems. So RN has that limitation and you have to tell users to manually add things into...
feel free to open a PR 🍻
@schlingding I totally agree with you and I'm also migrating everything to Swift Package Manager at work. **When Apple promotes an official way of doing something, suddenly all the other...