Old dependencies
See original GitHub issue- Jitsi Meet version: 2.10
- Platform: Android
We use jitsi with react-native. We got problem that every dependency conflicts each other and we excluded almost every:
implementation(project(':react-native-jitsi-meet')) {
exclude group: 'com.facebook.react',module:'react-native-sound'
exclude group: 'com.facebook.react',module:'react-native-vector-icons'
exclude group: 'com.facebook.react',module:'react-native-svg'
exclude group: 'com.facebook.react',module:'react-native-community-async-storage'
exclude group: 'com.facebook.react',module:'react-native-calendar-events'
exclude group: 'com.facebook.react',module:'react-native-fast-image'
exclude group: 'com.facebook.react',module:'react-native-linear-gradient'
exclude group: 'com.facebook.react',module:'react-native-webview'
exclude group: 'com.facebook.react',module:'react-native-google-signin'
exclude group: 'com.facebook.react',module:'react-native-background-timer'
exclude group: 'com.facebook.react',module:'react-native-locale-detector'
exclude group: 'com.facebook.react',module:'react-native-community_netinfo'
exclude group: 'com.facebook.react',module:'react-native'
exclude group: 'com.facebook',module:'hermes'
transitive = true
}
After we excluded all dependencies we succeed to start app. But now jitsi is crashing. Main reason of crashes: old dependencies. Also I found that some dependencies are forked. Why??? Repositories are empty.
Currently I know at least 2 libs that causes crashes for android:
- react-native-calendar-events
- react-native-community_netinfo
Can you update dependencies to recent versions?
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (4 by maintainers)
Top Results From Across the Web
Maven: Purge Old Dependencies from Local Repository
Maven: Purge Old Dependencies from Local Repository Java. ... Caching the old snapshot build artifacts consumes disk space.
Read more >Intellij keeps old dependencies : IDEA-255594 - YouTrack
The old dependency sticks around and is referenced in the project although mvn dependency-tree shows the new version. Enabling maven.always.remove.bad.entries ...
Read more >How to clean old dependencies from maven repositories?
Is there a way to clean all old dependencies? For example, if there is a dependency with 3 different versions: 1, 2 and...
Read more >Old dependencies are your second biggest technical debt
Being able to introduce changes into your application is incredibly important. Having outdated dependencies slows you down in various ways. Stay ...
Read more >Demography - Old-age dependency ratio - OECD Data
Definition of. Old-age dependency ratio ... The old-age to working-age demographic ratio is defined as the number of individuals aged 65 and over...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@deva-gopalani You have to make sure that compileSdkVersion and targetSdkVersion is set to 29. I forgot if setting minSdkVersion to 23 is necessary. But you can try it if not gonna work.
Also if you have this code in your android/build.gradle. make sure to set it to 29 as well.
I hear you, but I’ve been bitten by this package before. Multiple times. Someone adds some feature, which I don’t use, but then the code runs regardless and things break.
Keeping our dependencies up to date is something we strive for, but again, we need to be careful because the are many users relying on our app not breaking.
Regarding the package change. I’ll be blunt, that’s rubbish. It adds nothing, just churn as you can see, for literally no benefit.
We will update it, but we need to go through the changes to make sure nothing breaks.