Bug 125316 - "Attempt to get length of NULL Array" on first startup
Summary: "Attempt to get length of NULL Array" on first startup
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Android Viewer (show other bugs)
Version:
(earliest affected)
6.1.0.0.alpha1+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-15 22:54 UTC by Jim Avera
Modified: 2020-07-12 03:37 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Avera 2019-05-15 22:54:04 UTC
Description:
A pop-up appears when the app is started the first time saying something like
  "Attempt ot get length of Null Array"

I un-installed and re-installed, and the same thing happened.

The message does not appear on subsequent start-ups.

Steps to Reproduce:
1. Install Libre Office Viewer from the Google Play store
2. Press "Open" when the button appears in the Play Store (after iunstall finishes)

Actual Results:
A black pop-up says "Attempt to get length of a Null Array" or similar.

Expected Results:
.


Reproducible: Always


User Profile Reset: No



Additional Info:
Android 8.0.0, Samsung Galaxy s7
Comment 1 Xisco Faulí 2019-06-10 16:12:00 UTC
Hello Jim,
Does it happen only the first time you launch LibreOffice and then it launches fine ?
Comment 2 Timur 2019-06-18 15:22:10 UTC
I understand Jim already said it's just the first time. 
What I see, and I can't say if related, it's that Viewer is very slow on first file open, even if simple file. 
Jim, please test with daily master.
Comment 3 Michael Weghorn 2019-12-12 13:44:50 UTC
(In reply to Timur from comment #2)
> Jim, please test with daily master.

@Jim: Can you please test whether this still happens with a daily build from https://dev-builds.libreoffice.org/daily/master/Android-ARM@24-Bytemark-Hosting/ and document the result here?
Comment 4 Jim Avera 2019-12-12 21:09:39 UTC
> Jim, please test with daily master.

Can you point me to instructions for how to do that?   All I know how to do on Android is download what is in the Play Store...
Comment 5 QA Administrators 2019-12-13 03:43:28 UTC Comment hidden (obsolete)
Comment 6 Michael Weghorn 2019-12-13 08:10:15 UTC
(In reply to Jim Avera from comment #4)
> Can you point me to instructions for how to do that?   All I know how to do
> on Android is download what is in the Play Store...

One description is e.g. at https://www.technipages.com/install-apk-files-on-android .

You can find the latest APK (= "installer") at https://dev-builds.libreoffice.org/daily/master/Android-ARM@24-Bytemark-Hosting/ , in a directory named according to the date it was created.
E.g. to use the version built this night, you would download the APK at https://dev-builds.libreoffice.org/daily/master/Android-ARM@24-Bytemark-Hosting/2019-12-13_01.13.59/master~2019-12-13_01.13.59_LibreOfficeViewer-strippedUIEditing-debug.apk .

Please don't hesitate to ask if there are any questions.
Comment 7 QA Administrators 2020-06-11 03:53:46 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2020-07-12 03:37:52 UTC
Dear Jim Avera,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp