Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type RCTAgoraRtcEngineModule?
See original GitHub issueIssue Description
private fun engine(): RtcEngine? {
return reactApplicationContext.getNativeModule(RCTAgoraRtcEngineModule::class.java).engine()
}
private fun engine(): RtcEngine? {
return reactApplicationContext.getNativeModule(RCTAgoraRtcEngineModule::class.java)?.engine()
}
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Only safe or non null assserted calls are allowed on a nullable ...
The problem is, that you defined the ArrayList as nullable . You have two options here: don't define the variable nullable (this depends...
Read more >Only safe (?.) or non-null asserted (!!.) calls are allowed on a ...
Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type RCTAgoraRtcEngineModule? #334.
Read more >Safe calls(?.) vs Null checks(!!) in Kotlin - Suneet Agrawal
In Kotlin, the type system distinguishes between references that can hold null (nullable references) and those that can not (non-null references).
Read more >"Only safe or null-asserted calls are allowed on nullable ...
"Only safe or null-asserted calls are allowed on nullable receiver" after converting Java code with Map#get as receciver that would throw an exception...
Read more >Kotlin and null safety: Yet Again! | by Vinay Joglekar - Medium
or non-null asserted (!!.) calls are allowed on a nullable receiver of type User? user?.name = "Vinay". This is how you null- check...
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
@cemarguvanli it will be released this week.
Seems like it was fixed by @LichKing-2234, waiting for the release then.