pusher / pusher/pusher-websocket-react-native
Could not resolve com.google.code.gson:gson:2.7-SNAPSHOT.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 76
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
When building my react native project I get the following error, although it would appear to be an issue with oss.sonatype.org being down for the past few days
FAILURE: Build failed with an exception.
- What went wrong:
Could not determine the dependencies of task ':app:processDebugResources'.
Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
Could not resolve com.google.code.gson:gson:2.+.
Required by:
project :app > project :pusher_pusher-websocket-react-native
> Could not resolve com.google.code.gson:gson:2.7-SNAPSHOT.
> Unable to load Maven meta-data from https://oss.sonatype.org/content/repositories/snapshots/com/google/code/gson/gson/2.7-SNAPSHOT/maven-metadata.xml.
> Could not GET 'https://oss.sonatype.org/content/repositories/snapshots/com/google/code/gson/gson/2.7-SNAPSHOT/maven-metadata.xml'. Received status code 502 from server: Bad Gateway
Contributor 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.
Research direction
Start by reproducing the Android build and inspect how the pusher_pusher-websocket-react-native dependency resolves com.google.code.gson:gson:2.+. Check whether the snapshot metadata endpoint is still required; done means the project builds without the reported Gson resolution failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, react-native
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100