Feature request : Add FakeAppUpdateManager.

[kishanhitk]

First of all, thank you very much @jonasbark and the community for this amazing package. 🙇
I have one feature request. Currently, to test in_app_update implementation, we have to upload the app to Internal Sharing in Play Store, therefore it is not possible to test it in real-time while coding. So, it becomes a little bit difficult for novice developers like me.
Google has released FakeAppUpdateManager for Android to test InAppUpdate locally while coding. So, is it possible to add this feature to this package also?
Until then can you please suggest me the preferred way of testing inAppUpdate implementation in my app?

Thanks
@kishanhitk

[gabrieleolmi]

essential feature!!

[jonasbark]

I will have a think about this. You can only really properly test it by using the internal sharing method in the Play Store, which is also mentioned in the official docs.

[namanshergill]

I will have a think about this. You can only really properly test it by using the internal sharing method in the Play Store, which is also mentioned in the official docs.

Yeah, but if Google deemed it necessary to add the FakeAppUpdateManager, I think it only makes sense the plugin implementing the API provides it too.

This will also help with unit testing massively. Currently, trying to test this code requires the developer to make a lot of assumptions of what the class might return to mock the responses. Which, as you can see, can be wrong or change with time, thus breaking the tests without the developer potentially realising.