Ask Question Forum:
Model Library:2025-02-08 Updated:A.I. model is online for auto reply question page
C
O
M
P
U
T
E
R
2
8
Show
#
ASK
RECENT
←
- Underline
- Bold
- Italic
- Indent
- Step
- Bullet
- Quote
- Cut
- Copy
- Paste
- Table
- Spelling
- Find & Replace
- Undo
- Redo
- Link
- Attach
- Clear
- Code
Below area will not be traslated by Google,you can input code or other languages
Hint:If find spelling error, You need to correct it,1 by 1 or ignore it (code area won't be checked).
X-position of the mouse cursor
Y-position of the mouse cursor
Y-position of the mouse cursor
Testcursor
caretPos
Attachment:===
Asked by test test
at 2026-02-05 19:10:37
ModifyPoint:500 Replies:5 POST_ID:829375USER_ID:12446
Topic:
android;jave
as title
Author: test test replied at 2026-03-16 19:27:39
For Andorid OS, SDK 36, u need relayout ...
Author: test test replied at 2026-03-15 23:42:36
SHA1 may be different from creation of Android Stuido debug, apk file, and google play console, so use getAppSH1() function to show SH1 key on apps, then update SHA1 on google cloud/firebase.
Author: test test replied at 2026-02-05 19:36:00
delete debug.kestore at c:\users\yourname\.android to create new SHA1 cerficate
Author: test test replied at 2026-02-05 19:33:56
SHA1 will be valid on Google Cloud after u saved it, around 1 or 2-hour
Accepted Solution
Author: test test replied at 2026-02-05 19:32:20
500 points Excellent
check the development process on Android Studo
1-at window, c:\users\yourname\.android which will store debug.keystore
that is related to SHA1 cerificate fingerprint, Generate SHA1 as follow methods
A-u can use on studio , using gradle menu, run "gradle signing" command to get SHA1
B-on command line at app directory, c:\.....\app\gradlew signing
C-keytool -keystore c:\users\yourname\.android -list -v
2-Open Google console for your project, create client for OAuth, Select Android Applocation, save package name and SHA1
as u generated it above
3-Be Reminded, make sure, SHA1 cerficate is same at Google cloud and your apps on Studio..
U can use different /same SHA1 for different projects, if different SHA1, u can delete, debug.keystore at /.android, then run invaliate cache to get SHA1
4- For Legacy, Google-sign, it use"storage_bucket":"myapps.appspot.com" for storage
for most update version, it use "storage_bucket": "myapps.firebasestorage.app" , which are specified at google-services.json file at your apps on Firebase console.
now Both are using free plan "Spark" on Google Cloud, When storage quate is over limit, u need to upgrade topay-as-you-go Blaze pricing plan
5- If u don't need request ID token, just remove it as follows. that will be authencate the google APiI code easier
GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
// .requestIdToken("")
.requestEmail()
.build();
6- If u SDK version below or equal 34 version, Legacy Google-sign-in API still work Fine. When u upgrade to
SDK 35 version, u need re-code all Google-sign jave code.
....Done
