Missing dSYM no matter what - firebase

Firebase Crashlytics console lists this file as missing:
D79D73EB-C9BE-3D0A-B3F5-4D6E5BF6E3A0 1.1.1 (1084) Optional
So I successfully download symbols from
https://appstoreconnect.apple.com/WebObjects/iTunesConnect.woa/ra/ng/app/***/activity/ios/builds/1.1.1/1084/details
The UUID is present:
$ dwarfdump -u ~/Downloads/appDsyms/* | grep 3A0
UUID: D79D73EB-C9BE-3D0A-B3F5-4D6E5BF6E3A0 (arm64) /Users/gene/Downloads/appDsyms/d79d73eb-c9be-3d0a-b3f5-4d6e5bf6e3a0.dSYM
Then I upload it to Crashlytics, probably for the 10th time:
$ Pods/Fabric/upload-symbols -gsp GoogleService-Info.plist \
-p ios ~/Downloads/appDsyms/d79d73eb-c9be-3d0a-b3f5-4d6e5bf6e3a0.dSYM
Successfully submitted symbols for architecture arm64 with UUID d79d73ebc9be3d0ab3f54d6e5bf6e3a0 in dSYM: /Users/gene/Downloads/appDsyms/d79d73eb-c9be-3d0a-b3f5-4d6e5bf6e3a0.dSYM
Now I go back to Firebase Crashlitics console and still see the UUID as missing.
I did try to upload it as appDsyms.zip too, also successfully. And unzipped and upload individual files. Tried different ways of uploading maybe 10 times. All worked fine. But the UUID is still missing:
What am I doing wrong?

Apparently Crashlytics has been partially broken for at least 4 days:
https://groups.google.com/forum/?pli=1#!topic/firebase-talk/nO-NCq7p2iQ
I suppose they could not be bothered to tell us that it's been broken. The status dashboard shows "green" for the whole week.
Google, shame on you.

Related

How to extract the maps via AC Dashboard?

I ran into the problem that everything went well with the compilation and the database. But when I start the worldserver, I get an error
Loading world information...
> RealmID: 1
> Version DB world: ACDB 335.6-dev
Will clear `logs` table of entries older than 1209600 seconds every 10 minutes.
Using DataDir /azerothcore-wotlk/data/
WORLD: VMap support included. LineOfSight:true, getHeight:true, indoorCheck:true PetLOS:true
Map file '/azerothcore-wotlk/data/maps/0004331.map': does not exist!
exit code: 1
worldserver terminated, restarting...
worldserver Terminated after 1 seconds, termination count: : 6
worldserver Restarter exited. Infinite crash loop prevented. Please check your system
What could be the problem? I rechecked the permissions to the directory including the owner and everything is fine. Tried different paths DataDir, now it set to **DataDir = "/home/azcore/azerothcore-wotlk/data". I get an error, how to fix that?
**
First of all, if you only need to get latest maps compatible with AzerothCore you can download them from here.
Otherwise, change in your config.sh file CTOOLS_BUILD='all', afterwards, run again the build using
./acore.sh compiler build
This will generate the binaries to extract the data inside azerothcore-wotlk/env/dist/bin/.
Having the binaries you can follow the guide here to extract them manually, you only need to move the binaries into the WoW directory and run the binaries in the right order.

how to upload a tflite file to firebase test lab device via gcloud?

It is known that additional files can be uploaded via the other files flag in gcloud.
I am trying to use the firebase test lab performance application to check the performance of a network.
The command i run is:
gcloud firebase test android run --type=game-loop --app=bazel-bin/tensorflow/lite/tools/benchmark/experimental/firebase/android/benchmark_model_firebase.apk --device model=flame,version=29 --other-files=/data/local/tmp/graph=network1.tflite
The command crashes with the error:
ERROR: gcloud crashed (InvalidUserInputError): Could not guess mime type for network1.tflite
Is there a way to circumvent the problem or somehow pass the mime type to the command line ?
I found a crazy workaround. I renamed the tflite file to so so the mimetypes library gave it an octet stream mime type and everything worked.
gcloud firebase test android run --type=game-loop --app=bazel-bin/tensorflow/lite/tools/benchmark/experimental/firebase/android/benchmark_model_firebase.apk --device model=flame,version=29 --other-files=/data/local/tmp/graph=network1.so
Opened an issue in google: https://issuetracker.google.com/issues/196230363

Importing a firebase collection into BigQuery using fs-bq-import-collection fails

I have installed the new BigQuery export firebase extension on my firestore database and it works great.
Now I am trying to import the existing data in the collection by following the instructions on the extension but getting the error below.
https://github.com/firebase/extensions/blob/master/firestore-bigquery-export/guides/IMPORT_EXISTING_DOCUMENTS.md
Any ideas how to resolve this error?
Note: I ran gcloud components update to update to the latest gcloud versions
npx #firebaseextensions/fs-bq-import-collection
Importing data from Cloud Firestore Collection: members, to BigQuery Dataset: qmtbc_dev_export, Table: members_raw_changelog
Error unlinking journal file C:\Users\fullo\AppData\Roaming\npm-cache\_npx\10884\node_modules\#firebaseextensions\fs-bq-import-collection\lib/from-members-to-qmtbc-dev:qmtbc_dev_export:members_raw_changelog
after successful import: Error: ENOENT: no such file or directory, unlink 'C:\Users\fullo\AppData\Roaming\npm-cache\_npx\10884\node_modules\#firebaseextensions\fs-bq-import-collection\lib\from-members-to-qmtbc-dev:qmtbc_dev_export:members_raw_changelog'
---------------------------------------------------------
Finished importing 0 Firestore rows to BigQuery
---------------------------------------------------------
Error importing Collection to BigQuery: Error: EPERM: operation not permitted, unlink 'C:\Users\fullo\AppData\Roaming\npm-cache\_npx\10884\node_modules\#firebaseextensions\fs-bq-import-collection\node_modules\grpc\src\node\extension_binary\node-v64-win32-x64-unknown\grpc_node.node'
Update 1:
I have been stuck on this for over 24hrs now.
I have reinstalled nodejs to v12.13 and killed my virus checker, rebooted etc
No luck.
Also tried npm rebuild
The closest issues I have seen are:
https://github.com/phoenixframework/phoenix/issues/2464#issuecomment-325497850
https://github.com/phoenixframework/phoenix/issues/2464#issuecomment-328853460
Update 2:
I have uninstalled node and tried versions 8.16.2, 10.17 and 12.13
I deleted my npm and npm cache folders and reinstalled my global node packages.
Still no luck. I may try this method instead: https://cloud.google.com/bigquery/docs/loading-data-cloud-firestore
Update 3:
I have given up. It would be good to know if this script actually works for others.
It does work. You just need to go to the IAM page in the Google Cloud Platform dashboard and give the user enough rights. Add a role with enough permissions to create a BigQuery datasets.
you have to export GOOGLE_APPLICATION_CREDENTIALS json file first and then issue npx #firebaseextensions/fs-bq-import-collection command

Firebase error: symbolFileMappings:upsert: The uploaded file is not a valid Breakpad Symbol file

I am trying to upload a dSYM file to Firebase using this command:
./Pods/FirebaseCrash/batch-upload -i ./Info.plist -p ./GoogleService-Info.plist ./service-accounts/mtb.json 78*****C-5**4-3***-***C-00*********7
But each time I run this, I get back the following errors
./Pods/FirebaseCrash/upload-sym-util.bash:377: error: symbolFileMappings:upsert: The uploaded file is not a valid Breakpad Symbol file.
./Pods/FirebaseCrash/upload-sym-util.bash:378: note: symbolFileMappings:upsert: The metadata for the symbol file failed to update.
I have tried this link https://groups.google.com/forum/#!msg/firebase-talk/4829Sp1_uKY/IEC_T4-VBAAJ but haven't had any luck as it errors out to
usage: batch-upload [-hv] [-p google-service] [-i info] service-account-file {mach-o file|uuid}
Can someone help me on this one please?
Thanks
Apparently this bug relates to batch-upload script having problems with archives, so you would need to patch it manually.
Try the following:
Change extract_symbols_and_upload "$EXE" "$ARCH" "$BUNDLE" to
extract_symbols_and_upload "$EXE" "$ARCH" "$BUNDLE/$BNDL_PATH"
The dump_syms utility understands dSYM bundles but not archives,
curiously enough. This fix will go out with the next release.
Source

Systrace - error truncating /sys/kernel/debug/tracing/set_ftrace_filter: No such device (19) unable to start

I am currently working on a project which aims to find out what the system is doing behind a series of user interaction on the android UI. For example, if user click send button in Facebook Messenger, the measured response time for such action is 1.2 seconds. My goal is to figure out what the 1.2 seconds consist of. My friend suggested that I should take a look into 'Systrace'.
However, when I tried systrace on my HTC one M8, I have encountered some problems:
First, error opening /sys/kernel/debug/tracing/options/overwrite - no such file or directory. I solved this problem by building up the support of the kernel following http://opensourceforu.com/2010/11/kernel-tracing-with-ftrace-part-1/ and mount -t debugfs none /sys/kernel/debug. Then I could find the tracing directory. Besides, I set ro.debuggable=1 in file default.prop within Ramdisk and burn the boot.img into my phone.
Now I encounter another problem: when I run - python systrace.py --time=10 -o mynewtrace.html sched gfx view wm, the following error(19) pop up: error truncating /sys/kernel/debug/tracing/set_ftrace_filter: No such device (19). I don't know if the way my building up kernel support for systrace is incorrect or anything is missing.
Could anyone helps me out with this problem, please?
I think I have worked out the solution. My environment is Ubuntu 16.04 + HTC one M8. I will write the steps as followed:
open terminal and enter: $adb shell
(1) $su (2) $mount -t debugfs none /sys/kernel/debug. Now you should be able to see many directories under /sys/kernel/debug/. (You may cd into /sys/kernel/debug to confirm this)
New a new terminal and enter: dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img to generate the boot.img kernel image from your device.
Use AndroidImageKitchen to unpack the boot.img and find the default.prop within Ramdisk folder. Then change ro.debuggable=0 to ro.debuggable=1. Repack the boot.img and flash boot it to your device.
Once the device boot, under terminal, enter: adb root and message like: restarting adbd as root may pop up. Disconnect the USB and connect again.
cd to the systrace folder, e.g. ~/androidSDK/platform-tools/systrace and use:
python systrace.py --time=10 -o mynewtrace.html sched gfx view wm
Now you may able to generate your own systrace files.

Resources