Migrate to null-safety #24
Conversation
* Building a flutter android apk failed due to the android project being androidX compatible. Hence, updating the compileSdkVersion to 27 to enable androidX migration.
* In case of result.error from AppAvailability.java the result received on dart is not of type Map<dynamic, dynamic> instead it's a Platform Exception. Since, the type cast is explicitly on the invokeMethod call, this results in type cast exception. * Resolving this by storing the result in an immutable variable first and then typecasting.
Fix: Resolving Type Cast Error
|
@pichillilorenzo any updates on this? Is this library still maintained? |
|
Is anyone actively reviewing the PR? |
|
Is anyone reviewing this and going to merge? @pichillilorenzo |
|
any update on this? |
|
Hey folks, I writing a similar package, from here after some weeks I launch first release for Android only. I doing make a skeleton first to launch and open for public. But I warning, I need help to write for IOS platform. Thanks! |
|
@juliavi @Nei1eveN @GRBurst @sagargpt I did launch first release: https://github.com/LeonardoRosaa/have_app |
Hey, I recently refactored this whole package in Kotlin. Here's the link if you want to use it - https://github.com/Yash-Garg/AppCheck Works for both Android and iOS, including null safety. |
|
Great! Thanks. flutter_appavailability:
git: https://github.com/LeonardoRosaa/flutter_appavailability |
Starting pull request to migrate package to null safety version.
To do: