HelpDesk

HelpDesk Support System

DTLive - Flutter App (Android - iOS - Website ) Movies - TV Series - Live TV - OTT - Admin Panel

Q:

API FAIL WHEN CONNECTING WITH PURCHASE CODE

public

Document

24_02_2025_52_67bc98de3debb.png

All Replies

Viewing 153 to 156 of total 212 topics

Thabk you so much for the follow up and ur wonderful support..

Im still in work office so i will have to apply those steps when i reached home and will update you..

So sorry for the delay..


Thanks again for your wonderful support.

Hi,

I just wanted to check if my previous explanation helped clarify your doubt regarding Google Sign-In and Mobile OTP login. Were you able to follow the steps, or do you need any further assistance?

Please let me know so I can help you resolve this issue. Looking forward to your response!

Regards,
Mr. Priyank

You have not purchased the Blaze Plan yet.

Document

06_03_2025_20_67c9311e318f3.png

Regards,
Mr. Priyank

Hi,

I understand that Google Sign-In is working in debug mode but not in the release APK. This issue occurs because the SHA keys used for authentication in Firebase are different for debug and release versions.

Steps to Fix Google Sign-In in Release APK:

1️⃣ Upload Your App to the Play Store (Even in Internal Testing)

  • To properly configure Google Sign-In, you need to upload your app to the Google Play Console (even if it's just for internal testing).
  • Once uploaded, Google will generate four SHA keys under App signing in the Play Console.

2️⃣ Find and Add These SHA Keys in Firebase

  • Go to Google Play Console → Setup → App Integrity
  • Copy all four keys:
    • App Signing SHA-1 & SHA-256
    • Upload Certificate SHA-1 & SHA-256
  • Open your Firebase Console → Project Settings → Your Android App, and add these keys under SHA Certificate Fingerprints.

3️⃣ Download and Replace google-services.json

  • After updating the SHA keys, download the updated google-services.json file from Firebase.
  • Replace the old google-services.json file in your Flutter app.

4️⃣ Rebuild and Test

  • Now, generate a new release APK and test Google Sign-In and OTP login again.
  • It should work as expected.

Since your app is not yet on the Play Store, Google cannot verify the SHA keys for the release build, causing Google Sign-In to fail. Once you complete the above steps, it should work fine.

Let me know if you need any help with this setup! 😊

Document

06_03_2025_76_67c93049eb872.png

Regards,
Mr. Priyank

Viewing 153 to 156 of total 212 topics

Support is Online

Office hours

Monday - Friday
10:00 AM - 06:00 PM
IST (GMT +5:30)

  • Office time

    00:00:00 AM

  • Your time

    00:00:0 AM

Explore Our Support Documentation

Whether you're troubleshooting an issue or looking for step-by-step guidance, our resources are designed to empower you with the knowledge you need