BookLog Application: Resolving Errors Part2

#buildTogether Day19/100

I had a fun day today. It began with a morning walk, breakfast at my favorite place, and talking to my favorite person before the weekend :D I feel blessed ❤

Back to my resolving errors in the application. It's been a while since I did development and my coding neurons are taking a bit of time to tune in..😛

I fixed multiple errors that were happening… I did manage to go past the setMultiChoiceItems the error that I was getting on my ALertBuilder but now my application does not start...

Error01:

This error was happening for a long time and I got a workaround for this, which I have not been able to test since the application started giving more errors..

so I fixed this by unchecked typecast to CharSequence, Hopefully, it should work but remain to be tested.

Error02:

android.view.InflateException: Binary XML file line #22 in com.geek.booklog:layout/activity_library: Error inflating class fragment

This got magically fixed when I run my app on my actual device rather my emulator

Error03:

Error: ending session with error: user cannot perform additive schema changes without write access: additive schema change: adding schema for Realm table "Author", additive changes from clients are restricted when developer mode is disabled (ProtocolErrorCode=206)

This was really a silly error that I failed to acknowledge.. 🙈 I had given “Read” permissions true to all while “write” only to user's own partition, it turns out when you are making additive changes to the schema, you need to have “Write” permissions even with Development Mode On.

Error04:

kotlin.UninitializedPropertyAccessException: lateinit property realmList has not been initialized

Now, this is the error where I am stuck and not able to fix. I am following the Fragment Lifecycle, while still getting the error…

This is my BookList Fragment code:

This should be fixed if I do Synchronous Realm calls instead of Asynchronous but remains to be checked and I will follow that tomorrow… :D