Applied nullability check for Kotlin app. Issue creating because view or adapterview is null. It is fixed based on assumption from logs. Applied check for both month and year. Applying nullability check means if adapterview or view is null, it exiting the execution of it
Types of changes
What types of changes does your code introduce to frames-android?
Put an x in the boxes that apply
[X] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
Further comments
Currently,Without this fix also, not able to reproduce the crash. I am still working on that to crashing from kotlin external app.
Proposed changes
Applied nullability check for Kotlin app. Issue creating because view or adapterview is null. It is fixed based on assumption from logs. Applied check for both month and year. Applying nullability check means if adapterview or view is null, it exiting the execution of it
Types of changes
What types of changes does your code introduce to frames-android? Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
Currently,Without this fix also, not able to reproduce the crash. I am still working on that to crashing from kotlin external app.