Possible.

Dear Sir,

I waited patiently for more than one week and cooperated fully to resolve the issue. Instead of providing a working solution, you repeatedly denied the problem, shifted the blame to my environment, and refused a simple verification request APK generated with my URL.

During this process, I was told the issue was “my problem” and support was refused unless I followed your preferred method. This approach felt unprofessional and dismissive, especially after I invested both time and money.

The item remains unusable for me, and the issue was never resolved. Requesting a refund after one week of failed support is not forcing a refund it is exercising my right as a buyer under Envato policy.

My review reflects my genuine experience with the product and the support provided. I cannot change it unless the issue is actually resolved and a working solution is delivered.

I prefer to let Envato review all evidence and handle this matter fairly.

Regards.

please show us the error you are getting and how did you conclude that it is our product issue and not your environment issue. Have you successfully run any other flutter app before? Or your ide is showing any error in the code file?

The issue occurs immediately after setting up and running your provided source code, without any custom modifications. The project fails to generate an APK, which clearly points to a problem within the project configuration itself.

Requesting repeated environment verification without first addressing the reported build failure and logs does not reflect a professional support process. A published item is expected to function in a standard Flutter setup or clearly document any limitations.

There were no error logs provided and every time we requested an error log, the client kept repeating for a build with their url. We are not entitled to provide build for the product, we are only entitled to fix the error if any in our source code. We also connected to anydesk and we saw no development environment configured in clients pc. When we asked to configure their environment, they again asked for a build.

Have you verified the latest APK after your last update? The project uses outdated Flutter libraries, yet issues are blamed on clients instead of being fixed.

I request buyers to check all comments and shared URLs before purchasing many users are facing the same unresolved issues.

Current Lib in APK and there should be other one

cupertino_icons ^1.0.6 → 1.0.8, get ^4.6.6 → 4.7.3, logger ^2.0.2+1 → 2.6.2, smooth_page_indicator ^1.1.0 → 2.0.1, percent_indicator ^4.2.3 → 4.2.5, flutter_screenutil ^5.9.0 → 5.9.3, dio ^5.4.1 → 5.9.1, pretty_dio_logger ^1.3.1 → 1.4.0, shared_preferences ^2.2.2 → 2.5.4, firebase_core ^2.24.0 → 4.4.0, firebase_messaging ^14.7.10 → 16.1.1, awesome_notifications ^0.7.4+1 → 0.10.1, nb_utils 7.0.7 → 7.2.0, pinput ^4.0.0 → 6.0.1, animated_bottom_navigation_bar ^1.3.3 → 1.4.0, flutter_launcher_icons ^0.13.1 → 0.14.4, change_app_package_name ^1.1.0 → 1.5.0, rename_app ^1.3.2 → 1.6.5, flutter_stripe ^9.2.0 → 12.2.0, image_picker ^1.0.0 → 1.2.1.

I waited over one week, but the issue was never resolved. Instead, responsibility was repeatedly shifted elsewhere.

As a developer, I was able to identify and share a detailed list of outdated libraries used in this project. I believe it would be very difficult for a non-technical buyer to diagnose these issues or even understand the root cause.

This is a genuine concern that should be properly addressed, not dismissed.

Check this url and you know its not updated https://ik.imagekit.io/ww7a9w0t1x/Screenshot%202026-02-02%20181308.jpg

It’s funny that you are mentioning outdated package an issue. The documentation clearly mentions which flutter version is suitable for this project. If there’s no error then there’s no need to update packages or flutter. If you have any compatibility issue then you can raise the issue as unusable. Anyway, we will be updating our product soon. If you really need latest update of flutter, wait till the update

I would like to clarify that this is not merely a preference for “latest Flutter”, but a real build and compatibility concern.

the current APK clearly relies on multiple outdated dependencies, several of which are already deprecated or incompatible with current Android build requirements. This directly affects:

Build stability APK generation time Compatibility with modern Android SDKs Long-term maintainability for buyers

I have already shared a clear, verifiable list of outdated libraries with their current stable versions. This was done to help improve the product, not to argue about versions.

Unfortunately, instead of addressing these dependency issues, the responsibility was repeatedly shifted to the client side. I also waited over one week, during which no fix or updated APK was provided.

This is why I raised the concern publicly and asked other buyers to review comments before purchasing, as multiple users are facing similar unresolved issues.

and sir may i know which api is used for live

Yes. Please mail me mrsen007@gmail.com I will send details. Thanks

App updated Only

I’m sorry, I know the app was updated, but what’s the changelog and how to proceed to an existing installation/deployment?

Okay

I mean, can you please specify the changelog and how to update an existing page?