Documentation doesn't reflect default logfile save directory

larsiusprime / crashdumper

A cross-platform automated crash report generator/sender for Haxe/OpenFL apps.

MIT License

112 stars 33 forks source link

Documentation doesn't reflect default logfile save directory #18

Open Draknek opened 9 years ago

Draknek commented 9 years ago

The readme says "By default will write to your program's own directory", but I found it actually writes to SystemPath.applicationStorageDirectory. Made me think for a long time it wasn't working!

larsiusprime commented 9 years ago

Whoops, documents need to be updated.

hopewise commented 8 years ago

My android is not rooted, that's sad, I can't view /data/data/com.myapp/files How can I set the path to development folder ?

jarbot commented 8 years ago

I'm still trying to find the crash dump file on the android file sys. But I know in order to browse the android file system on a non-rooted phone you need to do the following:

when you run your android build make sure you pass the -debug flag (openfl build android -debug)
get into the adb shell: a. adb shell b. cd data c. run-as com.your.package

You should be able to list folder contents then.

larsiusprime commented 8 years ago

Sorry about any pain here; I don't actually own a mobile device so I'm dependent on others for feedback related to those targets.

jarbot commented 8 years ago

I triggered a crash on android and can't seem to locate the crash dump file.

I'm looking in here: /data/data/com.my.package/

I see the following folders: cache files lib

I'm using the default path which I traced out to see what it was: log/vws_2015-10-27_11'21'13_CRASH/

I'm assuming thats relative to the applicationStorageDirectory

larsiusprime commented 8 years ago

It should be, yes, what happens when you trace out System.applicationStorageDirectory ?

jarbot commented 8 years ago

Found it! I was confused by a folder named 'null'

Here is the full path: /data/data/com.my.package/files/null/log/errors

trace SystemPath.applicationStorageDirectory: /data/data/com.my.package/files/

I will investigate further where null is coming from. Thank you for the help.

larsiusprime commented 8 years ago

sounds a lot like a variable is being appended to the path, whose value is "null", I wonder if this is maybe related to you not having a project id?

jarbot commented 8 years ago

yep. you're probably right I just need to track down what I'm not setting properly. It's tricky to get the crash dump files off of the device. Still trying to figure it out. I'll post back here when I have it working.

jarbot commented 8 years ago

There are multiple ways of pulling data from a device using adb backup etc. The following is what worked for me. It requires your android build to be debuggable.

adb shell
run-as com.my.package
chmod -R 775 files/

After exiting the adb shell run the following:

adb pull /data/data/com.my.package/files/null/log/errors/ ./

You'll need to replace 'null' with something potentially. I haven't figured that part out yet. If that pull doesn't work browse the file system to locate the right path to your crash dump files.