command:firebase crashlytics : symbols:upload failed

[April-studio]

[REQUIRED] Environment info

**firebase-tools:9.23.0

**Platform:Windows,

[REQUIRED] Test case

i want to generate a Crashlytics-compatible symbol file and upload it to Firebase servers by running the following Firebase CLI command:firebase crashlytics : symbols:upload --app=FIREBASE_APP_ID PATH/TO/SYMBOLS Unfortunately, it did not generate a Crashlytics-compatible symbole file,[CRASHLYTICS LOG DEBUG] say like this:No native libraries found at [My Output Path].

[REQUIRED] Steps to reproduce

1.In My UnityEditor2018.4.30f,I build my apk directly from the Unity Editor and i confirmed the checkbox for Create symboles.zip is checked in the Build Setting dialog.Once my build has finished.I got the file like this [myAppName].symbols.zip. 2.I run the firebase-tools-instant-win.exe,and run the command like this firebase crashlytics : symbols:upload --app=1:311642575325:android:0cc308591bb795f3c72634 D:/AnimeColorClient/TapAnimeColor-1.8.2-72-CrashTest-1.8.2-v72.symbols.zip

[REQUIRED] Expected behavior

generate a Crashlytics-compatible symbol file and upload it to Firebase servers

[REQUIRED] Actual behavior

The following error was found in the debug log file:

[abeisgoat]

Can you please provide the firebase-debug.log so we can dig in? Thanks!

[April-studio]

the file name "firebase-debug.log" can not find it,may be the tool:firebase-tools-instant-win.exe can not generate the "firebse-debug.log"

[WeiLingQiang]

Can you please provide the firebase-debug.log so we can dig in? Thanks! firebase-debug.log I had the exact same problem

[yuchenshi]

Hi, thanks for filing this issue! We are unable to promise any timeline for this, but if others also have this issue, adding a +1 on this issue can help us prioritize adding this to the roadmap.

(Googler-only internal tracking bug: b/229028745)

[PhoenixLin1991]

+1

[characterx]

Hi, I had a similar issue and while randomly trying things I ran the Firebase CLI as administrator and things started to work. Maybe the results just correlated but I think it worths trying. Maybe the problem occurs because your files are in D:\ but since I cannot reproduce my error I cannot be sure.

[pigerj]

+1

[lanyantao]

+1

[lanyantao]

Resoved，i didt set jdk environment path。you try it

[lanyantao]

@characterx @pigerj @PhoenixLin1991

[pigerj]

thank you. we reinstall java and its all working now. how long after uploading the symbols will it take for crashes to show with meaningful stack trace?

On Thu, May 26, 2022 at 6:40 AM lanyantao @.***> wrote:

@characterx https://github.com/characterx @pigerj https://github.com/pigerj @PhoenixLin1991 https://github.com/PhoenixLin1991

— Reply to this email directly, view it on GitHub https://github.com/firebase/firebase-tools/issues/3930#issuecomment-1138117781, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQXDPG46W5FFYRLFD6JBI3TVL3XBJANCNFSM5JLBUXZA . You are receiving this because you were mentioned.Message ID: @.***>

[lanyantao]

thank you. we reinstall java and its all working now. how long after uploading the symbols will it take for crashes to show with meaningful stack trace? … On Thu, May 26, 2022 at 6:40 AM lanyantao @.> wrote: @characterx https://github.com/characterx @pigerj https://github.com/pigerj @PhoenixLin1991 https://github.com/PhoenixLin1991 — Reply to this email directly, view it on GitHub <#3930 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQXDPG46W5FFYRLFD6JBI3TVL3XBJANCNFSM5JLBUXZA . You are receiving this because you were mentioned.Message ID: @.>

unfortunately, dont get the stack trace info now, sad!

[vahagn-harutyunyan]

+1

[mrichards]

For folks that are struggling with uploading symbols on Windows, I believe we've isolated a Windows-specific path resolution issue and will try to have it fixed in the next release. There may be an effective workaround to cd into the directory containing the symbol file and run the firebase command from there. The path resolution issue seems to be avoidable if there's only a base filename and no other relative or absolute path information.

@lanyantao and @pigerj You should see symbolicated stack traces within a few minutes of uploading symbols, but only for new crashes. Previous unsymbolicated crashes will not be reprocessed.

If symbols appear to be uploading correctly yet you are still experiencing an issue with missing or unsymbolicated stack traces, please ensure you're on the latest version of the Firebase Unity SDK (9.4.0). If the problem continues, it would be helpful to see the on-device logcat output for FirebaseCrashlytics and libcrashlytics logtags.

[BIGCATDOG]

Still get trouble for this. `[CRASHLYTICS LOG DEBUG] Uploading native symbol files from directory: /var/folders/s3/sqywjqvn5mj3rz267b3d9llc0000gn/T/crashlytics-9b0ea35a-a957-4957-b4ff-fc6e1e0dac0d/nativeSymbols/1-528575156391-android-4d942918bce2235db24b82/breakpad [CRASHLYTICS LOG DEBUG] PUT file: /var/folders/s3/sqywjqvn5mj3rz267b3d9llc0000gn/T/crashlytics-9b0ea35a-a957-4957-b4ff-fc6e1e0dac0d/nativeSymbols/1-528575156391-android-4d942918bce2235db24b82/breakpad/game-arm64-720d26e926ae424eb76b4d711cd47dbfcec0747a.gz to URL: https://firebasecrashlyticssymbols.googleapis.com/v1/project/-/app/1:528575156391:android:4d942918bce2235db24b82/upload/breakpad/720d26e926ae424eb76b4d711cd47dbfcec0747a [CRASHLYTICS LOG DEBUG] PUT headers: [CRASHLYTICS LOG DEBUG] User-Agent = firebase-cli;crashlytics-buildtools/2.9.1 [CRASHLYTICS LOG DEBUG] X-CRASHLYTICS-API-CLIENT-TYPE = firebase-cli;crashlytics-buildtools [CRASHLYTICS LOG DEBUG] X-CRASHLYTICS-API-CLIENT-VERSION = 2.9.1 java.net.UnknownHostException: firebasecrashlyticssymbols.googleapis.com: nodename nor servname provided, or not known at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929) at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324) at java.net.InetAddress.getAllByName0(InetAddress.java:1277) at java.net.InetAddress.getAllByName(InetAddress.java:1193) at java.net.InetAddress.getAllByName(InetAddress.java:1127) at com.google.firebase.crashlytics.buildtools.reloc.org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45) at com.google.firebase.crashlytics.buildtools.reloc.org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:112) at com.google.firebase.crashlytics.buildtools.reloc.org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373) at com.google.firebase.crashlytics.buildtools.reloc.org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:394) at com.google.firebase.crashlytics.buildtools.reloc.org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237) at com.google.firebase.crashlytics.buildtools.reloc.org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185) at com.google.firebase.crashlytics.buildtools.reloc.org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) at com.google.firebase.crashlytics.buildtools.reloc.org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) at com.google.firebase.crashlytics.buildtools.reloc.org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) at com.google.firebase.crashlytics.buildtools.reloc.org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) at com.google.firebase.crashlytics.buildtools.reloc.org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108) at com.google.firebase.crashlytics.buildtools.reloc.org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) at com.google.firebase.crashlytics.buildtools.api.RestfulWebApi.sendFile(RestfulWebApi.java:100) at com.google.firebase.crashlytics.buildtools.api.RestfulWebApi.uploadFile(RestfulWebApi.java:119) at com.google.firebase.crashlytics.buildtools.api.FirebaseSymbolFileService.uploadNativeSymbolFile(FirebaseSymbolFileService.java:35) at com.google.firebase.crashlytics.buildtools.Buildtools.uploadNativeSymbolFiles(Buildtools.java:301) at com.google.firebase.crashlytics.buildtools.CommandLineHelper.executeUploadSymbols(CommandLineHelper.java:194) at com.google.firebase.crashlytics.buildtools.CommandLineHelper.executeCommand(CommandLineHelper.java:120) at com.google.firebase.crashlytics.buildtools.CommandLineHelper.main(CommandLineHelper.java:65) at com.google.firebase.crashlytics.buildtools.Buildtools.main(Buildtools.java:111)

Error: java command failed with args: -jar,/Users/alex/.cache/firebase/crashlytics/buildtools/crashlytics-buildtools-2.9.1.jar,-symbolGenerator,breakpad,-symbolFileCacheDir,/var/folders/s3/sqywjqvn5mj3rz267b3d9llc0000gn/T/crashlytics-9b0ea35a-a957-4957-b4ff-fc6e1e0dac0d/nativeSymbols/1-528575156391-android-4d942918bce2235db24b82/breakpad,-verbose,-uploadNativeSymbols,-googleAppId,1:528575156391:android:4d942918bce2235db24b82,-clientName,firebase-cli;crashlytics-buildtools

Having trouble? Try firebase [command] --help

[mrichards]

@BIGCATDOG Are you behind a proxy or were you on a bad internet connection? Please check those things.

OP's issue was "no native libraries found" error. If your UnknownHostException persists, please open a new issue. Thank you!

[mrichards]

We released the Crashlytics proxy fix in Firebase CLI v11.10.0.

We haven't been able to reproduce the Windows path resolution issue locally (despite trying on several similar configurations), but the workaround mentioned earlier seems to be sufficient for other customers who have had similar problems. I'm going to close this issue for now; if anyone is completely blocked on uploading, please open a ticket with Firebase Support.