Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unusual error message when retrieving data set and binding to layout
See original GitHub issuehi, recently with the lastest plugin I have been getting this message TypeError: null is not an object (evaluating 'firebase.instance.childByAppendingPath') somewhat frequently when livesyncing and retrieving images from the database. Anyone else getting this? It blocks me from getting the data.
Issue Analytics
- State:
- Created 7 years ago
- Comments:39 (23 by maintainers)
Top Results From Across the Web
Error using databinding in android - Stack Overflow
I ran into this error and finally discovered it was because I had a duplicated android xml namespace. The DataBinding library in Android...
Read more >Layouts and binding expressions | Android Developers
Data binding always creates a listener, which it sets on the view. When the event is dispatched, the listener evaluates the lambda expression....
Read more >Data binding in Android - Siva Ganesh Kantamani - Medium
Sometimes when you create a new layout and try to access its data-binding reference from one of the source class it'll show cannot...
Read more >Advanced Data Binding in Android: Layout Expressions
Learn how to use layout expressions for data binding in Android and make your code more concise and less error-prone.
Read more >Database Engine events and errors - SQL Server
Consult this MSSQL error code list to find explanations for error messages for SQL Server database engine events.
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 Free
Top 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
@kushMehra That’s great to hear! I think during livesync (or whatever triggered the issue) the
initmethod is not invoked (before or at all) thefirebase.instanceproperty was accessed (it would beundefinedin that case).So I simply removed my custom
firebase.instancecache as it’s hardly better than grabbing the Firebase instance from the native SDK (which is neverundefined).Thanks @EddyVerbruggen, it works! Would you mind sharing what was the issue?