[Major Refactor] Need to split geofire-android and geofire-java into two repos
See original GitHub issueWhen trying to set the setLocation on the GeoFire object runs into following issue at run time
No virtual method setValue(Ljava/lang/Object;Ljava/lang/Object;)Lcom/google/firebase/tasks/Task; in class Lcom/google/firebase/database/DatabaseReference; or its super classes (declaration of 'com.google.firebase.database.DatabaseReference' appears in (apk file )
Using the GeoFire 2.0.0 SNAPSHOT version. Firebase version: com.google.firebase:firebase-database:9.0.2
Issue Analytics
- State:
- Created 7 years ago
- Comments:33 (11 by maintainers)
Top Results From Across the Web
The Big Refactor - Medium
The project had initially started with separate repositories for each of the components, however a decision was made to combine these ...
Read more >Code Refactoring Best Practices: When (and When Not) to Do It
Applying the Red-Green-Refactor method, developers break refactoring down into three distinct steps: Stop and consider what needs to be ...
Read more >Great Tools for Engineers: Refactoring Across Multiple Code ...
This post is about working with code that lives in many separate code repositories, while still being productive and efficient in the process!...
Read more >3 Ways to Refactor Your Code in IntelliJ IDEA
Simplifying your code has lots of advantages, including improving readability, tackling technical debt, and managing ever-changing requirements.
Read more >git - What's the best way to handle refactoring a big file?
You have correctly understood that this is not so much a technical as a social problem: if you want to avoid excessive merge...
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
hi, so it appears that this bug only manifests itself when we call setLocation without the GeoFire.CompletionListener().
If you call geoFire.setLocation(“X marks the spot”, new GeoLocation(x, y), new GeoFire.CompletionListener() { } then it works. (Im using geofire 2.3.0)
I change it from
com.firebase:geofire-android:3.1.0
tocom.firebase:geofire-android:2.1.1
works fine 😃