Thank you for your patience.

The video size problem will be fixed in the next 1–2 updates.

Currently:

YouTube, Vimeo or embedded videos are played inside a WebView.

Other videos are played using Pod Player.

Both players automatically maintain the original video dimensions to ensure the full content is visible without being cut from any side. If we force a different aspect ratio, the video may be cropped vertically or horizontally, which would result in some content being cut off.

We are working on improving the player layout to make it more responsive while keeping the full video visible.

Thank you for your patience and support.

There is no problem playing the video with YouTube, when I put the video URL, the wrong size is played

video quality: URL

Thank you for your feedback.

We have checked the video_quality (URL type) issue. Currently, the app uses a fixed video aspect ratio for URL-based videos, which may cause incorrect sizing on some devices.

In the upcoming 1–2 updates, we will improve this by adding:

Fit to Screen option

Additional aspect ratio controls

Better responsive scaling for different device sizes

This will ensure the video displays properly without distortion or incorrect sizing.

Thank you for your patience

Thanks for your work. Regarding the web app DRM, can the movie links be hacked or viewed in the browser console for hacker?

Thank you for your question. Regarding the web app DRM: At present, the movie stream URLs can potentially be inspected through the browser’s developer tools (console/network tab). Since the content is delivered to the client side for playback, a technically skilled user may be able to view the stream URL. However, enhanced DRM protection is already planned and will be included in our next major updates.

ok thank you

There is no hardcoded user limit in the Streamit Laravel script. The system can handle unlimited registered users.

The number of simultaneous users depends entirely on your server resources (CPU, RAM, database performance, PHP workers, caching, etc.).

For high traffic, we recommend using a VPS/Dedicated server with Redis and proper server optimization.

In short, the capacity is determined by the hosting environment, not by any built-in script limitation.

Thanks for your message.

No, the CinetPay gateway payment is not available in the new 2.1.0 release of the Streamit – OTT Live Video Streaming App Built with Flutter. We plan to add it in upcoming update.

hello in this last version you add cinetpay for mobile app

Hello,

We have only implemented minor fixes in the 2.1.1 version update. The remaining changes will be included in the next release (2.2.0).

Now you can check change log is updated.

We understand your concern, and we want to clarify the status of the points you raised.

Video stops when adjusting phone volume: We have carefully tested this behavior on our side across multiple devices, and it is working correctly. Because of this, it appears to be device-specific or OS-level behavior rather than a core app issue. If you continue experiencing it, please share your device model, OS version so our team can investigate more precisely.

Incorrect video player size: As previously communicated, this issue has already been acknowledged by our team and is planned to be addressed according to our development timeline. We did not commit that it would be included in the immediate update, but it is scheduled for an upcoming release.

Please be assured that your reported issues are not being ignored. We address fixes based on overall impact, technical complexity, and release planning to maintain stability for all users.

Thank you for your patience.

Xiaomi Note 12 Android 15

Xiaomi note 14 Android 15

Samsung A56

Thank you for sharing the device details.

We have tested the same scenario on multiple devices across different brands, including Samsung, Redmi, Oppo, Vivo, Motorola, Oneplus and others. On most devices, the video playback works as expected when adjusting the system volume.

However, we observed that on some Redmi/Xiaomi devices, the issue does occur. We will find the root cause as device-specific behavior, our team will fix it.

This issue will be resolved in the next update.

Thank you for your patience and for helping us improve the product.

Hello,

Thank you for reaching out regarding the reported issues.

Please find the current status below:

1. Subtitles issue has already been fixed in version 2.0.0.

2. The audio switching feature will be implemented according to our development timeline. If this feature is urgent, you may connect with our customization team for priority implementation. If you would like to discuss this requirement in more detail, you can join using the link below: https://teams.live.com/l/invite/FEAh18wQSi9roOzkA8

3. Video size issue in the player has been identified and will be fixed in an upcoming update, according to our development timeline.

4. TMDB images not being stored/displayed on the host is currently under review. Our team is checking this issue and will resolve it in an upcoming update.

We will keep you informed about progress and upcoming releases. Thank you for your patience and continued support.

The subtitle problem is still there in the demo version(2.0.0) you installed, check it yourself and send a screenshot

Hello,

We’ll check the issue from our side, and if the subtitle problem is present, we’ll fix it accordingly.

Thank you

Hello,

Apple has reviewed the app and rejected it due to Guideline 4.3(a) – Design – Spam. Their feedback states that the app appears similar to other apps on the App Store with only minor differences.

This happens because the app was originally built on a template, and Apple requires apps to offer unique content and functionality.

Next Steps:

you can highlight and document all the customizations and redesigns you’ve implemented to show Apple that the app is distinct.

If needed, you can make additional improvements to the design, features, and user experience to further differentiate it.

Once you prepare this information, you can submit it to Apple for reconsideration.

Let us know if you’d like us to proceed with this so the app can be approved.

Thank you for your interest and kind words about our project.

Currently, our app supports M3U8 (HTTP links) and MKV links for live streaming, movies, and TV series. At this time, DASH / MPD links (with or without licenses) are not supported.

However, DASH / MPD support is planned for a future update, and we are actively considering it based on user demand.

Please feel free to reach out if you have any further questions—we’ll be happy to assist you.

Thank you for sharing your feature suggestions. We will consider these enhancements for inclusion in a future update of the application as part of our ongoing improvements.

Thank you for your feedback and for choosing our app.

It would be great if there was a system to report movies and series that couldn’t be viewed.

Thank you for your suggestion.

We appreciate your idea of adding a system to report movies or series that cannot be viewed. This is a valuable feature that can help us quickly identify and resolve content issues.

We will review this request with our development team for potential inclusion in a future update as part of our ongoing effort to improve the user experience.

Thank you again for your feedback and support.

To review this issue, we kindly request you to raise a ticket on our support platform: https://iqonic.desky.support/ Our support team will look into the matter and update you accordingly.

Submitted

Okay Thanks. Our team will check and get back to you as soon as possible so you can communicate there for better assistance.

Thank you for taking the time to share your detailed feedback. We truly appreciate your interest and understand your concerns. Please find our responses below:

Subtitles & Audio Switching We acknowledge the issue with subtitle synchronization in the current version. Our development team is actively working on fixing this. Support for multiple audio tracks (audio switching) is already planned and included in our roadmap. This feature will be introduced in a future update.

Video Player Size / Layout Issue We are aware that the video player size is not rendering correctly on some devices. This issue has been identified and will be resolved in our upcoming update.

TMDB Images Not Stored on Host Currently, TMDB images are loaded directly from TMDB. We understand the requirement to store these images on your own host, and this improvement will also be addressed in a future update.

Playback Stops When Changing Device Volume: Thank you for reporting this newly discovered issue. Our team is reviewing it, and it will be investigated and fixed in an upcoming release.

We sincerely apologize for the inconvenience caused. Your feedback helps us improve the product, and we are committed to delivering better stability and features in future updates.

Thank You!

When will the next update be released to solve the problems I mentioned?

Thank you for your follow-up.

We understand your concern and would like to clarify our current plan:

TMDB images storage on host and the playback issue when adjusting device volume have already been addressed and are scheduled to be included in the next update.

The remaining items, including subtitle improvements, audio track switching, and video player size/layout enhancements, are currently under internal discussion with our development team and will be aligned with our product roadmap based on feasibility and testing.

At this stage, we are unable to provide an exact release date, as updates are released only after thorough development and quality assurance to ensure platform stability.

We truly appreciate your patience and feedback, as it helps us continuously improve the product. All confirmed fixes and enhancements will be announced through official update notes once released.

Thank you for your understanding and for considering our product.

At this moment, Wasabi Cloud is not supported out of the box in the current system.

To use Wasabi, code-level configuration and customization will be required on the project, including storage driver adjustments and endpoint handling. This will involve additional development and testing effort.

Hello Naba,

As you can see in the attached image link https://prnt.sc/AIP8-dY6JFQU , we replied 6 days ago, but we did not receive any response from your side.

Regarding the issues you mentioned — none of your points were actual bugs in the original product code. We have already explained everything multiple times with proper clarification.

We also found that your code was totally customized on your side, which is not covered by our support policy. Still, we gave your ticket priority and reviewed each point one by one, providing proper assistance even for the customized code. You have not replied to support for many days, yet you posted comments and a review claiming we did not provide updates.

We have informed you many times that instead of commenting repeatedly, you should reach us through the support ticket. When you reply in the ticket, we can assist you faster and more efficiently.

You keep mentioning “20 issues,” but we have already provided clear explanations for all the points you raised, including your last list of 21–25 items. All of this is available in your chat history.

If you find any bug or issue in our product’s original code, you can reach out to us anytime through the support ticket — we are always ready to help you.

So, we kindly request you not to post misleading comments without replying to the support ticket. Such comments may misguide new buyers, even when the product is working properly.

Also, the low-star review you added is based on wrong blame. You have not reached out to us for the last 6 days, and as per our policy, we cannot make the entire chat public. If you refer to the previous chat, you will clearly see that your code was customized on your side, and still, we investigated and assisted you on every point.

Important Note: We have already investigated and found that your code was customized on your side, which is why these issues occurred — not because of any bug in the original product. As per our support policy, we do not provide help for issues caused by custom code. Still, we went beyond our support policy and provided you with proper assistance. Kindly understand this matter carefully.

bhai tame sum vata karo cho… I haven’t done any customization in the code. Show me any one. As per the last reply. Your team send me 2 changes to be done inside the code. The first change i had done, the second one is not available in the original code.

I need support brother, I know you are doing great, Check all my previous comments with SANJAYSA1990 Account, i always supported you. But still SMTP not Working, payment Gateway not working, After otp confirmation black screen coming and many more. If it requires additional support I will pay for it. But i can’t wait anymore.

Replying long long threads is just consuming time, instead of that consumption. Please guide me to solve them.

Hello,

We have already told you again and again that the issue you are facing is not caused by the changes we made, and we have already provided you with the correct images and code multiple times.

The second change we shared must be added manually to your code. Since this code is missing on your side, we clearly explained in the support ticket that you must add this code. But you misunderstood, and instead of adding the code, you kept searching for it in your files. Please try to understand what we are explaining.

We have already given you the full explanation inside the ticket, but I am explaining it here again one more time. However, please make sure that from now on, you do not continue the same discussion in both comments and support tickets.

Explaining the same thing twice in two different places becomes very time-consuming, and we have already requested before that all communication should remain only inside the support ticket. That helps us track everything properly and assist you faster.

If you continue posting the same matter in both places (comments + support), then we will respond only inside the support ticket, not in comments next time. We also have to manage other customers, so please cooperate and use only the support ticket, where we already provide you with complete assistance.

Now, here is the explanation for your issues (already given in the ticket, but repeating once again):

• Neither SMTP is working

I want to clarify that the entire flow is working perfectly on your setup.

When we added our SMTP credentials, everything worked fine, and emails were delivered successfully — as shown in Image 2 in the support ticket. This clearly proves that there is no bug in your product code or in our original code.

The issue is completely because of wrong SMTP configuration on your side. Once you correct your SMTP details, everything will start working exactly the same on your server.

You can check this working proof here: https://prnt.sc/rRQLytR_GBNN

• Payment Gateway Not Working

All payment gateways in our product are fully working. If you are facing issues, it is because the keys you entered are incorrect or incomplete. Once you add the correct test/live keys in your Admin Panel, everything will work. This is a configuration issue by your side, not a product bug.

• After OTP Confirmation → Black Screen Issue

As we already explained, this issue occurs because two files on your side are not updated. We have already provided the correct updated files in the support ticket.

If you replace those files exactly as instructed, the issue will be solved immediately.

We genuinely appreciate it if you try to understand this matter clearly and continue the conversation only inside the support ticket.

Throughout the entire chat, you can clearly see that we have constantly provided you with proper help and full assistance.

Thank you.

Hello, thank you for reaching out.

To ensure smooth performance:

Hosting Recommendation: Use VPS or cloud hosting (e.g., DigitalOcean, AWS) rather than shared hosting.

Minimum Server Specs: RAM: 2–4 GB (4 GB recommended)

Storage: SSD with 10–20 GB minimum (depending on your video content)

CPU: Standard 2-core+ server CPU or higher

Large Video Hosting: Amazon S3 is fully supported. Estimated cost: ~$0.023/GB storage + ~$0.09/GB data transfer.

Performance Tip: Pair S3 with a CDN for faster global delivery.

Hello,

Thank you for your message!

Yes, reskinning in terms of setup and branding is available for both the Laravel backend and the mobile app.

For further details on pricing and the full process, our business executive will assist you directly on Microsoft Teams. Please connect with them using the link below: https://teams.live.com/l/invite/FEAh18wQSi9roOzkA8

They will guide you through the complete reskin/branding options and provide accurate costing.

We appreciate your cooperation!

We appreciate your efforts and the details you shared.

To investigate this correctly, we need to confirm the mobile app version you are testing on. On our side, we checked the same scenario using Android app v1.6.3, and the genres are displaying as expected.

You can download the version we tested here: https://limewire.com/d/4hgrK#fPQcJIgpOI

Once you confirm your app version, we can proceed with deeper debugging.

yes, 1.6.3 installed app

We’re not facing the same issue on our side, but thank you for taking the time to share the details. Our testing phase is already in progress, and we will ensure this scenario is covered along with other test cases.

We have also tested the same version v1.6.3, but installed directly from the Play Store.

We suggest uninstalling your current build and installing a fresh copy from the Play Store to rule out any build-specific issues. Here is the link: https://play.google.com/store/apps/details?id=com.iqonic.streamitlaravel&pcampaignid=web_share

Thank you for reporting these issues.

We’ve reviewed the app on our end, and non-subscribed users are correctly being redirected to the subscription purchase screen before accessing premium content. We also tested reviews and ratings, and they are posting successfully.

To investigate your specific case further, could you please reach out to us through our official support platform?

With an active support period, our technical team will be able to look into the premium access issue you’re facing, as well as the 500 internal server error on comments. Once the required details are shared in the ticket, we’ll make sure our team assists you thoroughly and resolves everything as quickly as possible.

Thank you for your cooperation!

Yes, it will work fine. The 1.6.3 update contains only mobile-side improvements, and there are no breaking changes with the web version (1.6.2). Both versions are compatible, so you can proceed with updating the mobile app safely.

We are planning to include this in the next update, which is expected to be released next month.

However, if you require this feature urgently, you may have it implemented by your own developer or freelancer. Alternatively, you can choose our customization service, and we will develop it for you. Otherwise, you can wait for the official update release.

Thank you very much. What do you plan to update next month?

Coming in the Next Release:

Improved performance through code optimization & stability

Modern and refined UI upgrades

Integrated Bunny Stream / Bunny Storage support

Enhanced media library for better asset management