Trouble with Permissions and Code Execution at the App Front End

foetusmachine · June 17, 2021, 7:41am

Hi,
I'm having some strange issues. I can't work out if i've screwed up some code accidentally with sloppy fingers or if there's something else going on.

This is the code from my app startup:

and:

Basically, I want the permission granted before I continue with any further code execution (the initialize routine). However, this is what my screen grab looks like:

I can't work out why i'm getting this bad arguments error. If I click allow, the error persists and if if I deny, the app closes.

Any ideas on what may be going on? Could a clock timer be firing off some code? Something else?

TIMAI2 · June 17, 2021, 7:59am

Two things

Looks like you have an issue with an empty variable or list you have created (these are set before Screen1.Initialise)

Your initialise event will not run second time after giving permission because no permission is granted. You will need to add more logic to handle this.

Patryk_F · June 17, 2021, 8:03am

Show all blocks.

foetusmachine · June 17, 2021, 8:14am

I found one, but it hasn't made any difference.

I do have quite a few lists going on. What kind of issues should I be looking for?

This is okay... I think. I call other specific routines throughout the code.

foetusmachine · June 17, 2021, 8:15am

I'd love to narrow it down a bit for you first!

TIMAI2 · June 17, 2021, 8:16am

Blocks unreadable

foetusmachine · June 17, 2021, 8:17am

@TIMAI2 I know. Hence, my comment about trying to narrow the problem down a bit for everyone.

It was a tongue-in-cheek comment. My apologies.

TIMAI2 · June 17, 2021, 8:20am

Show all the variables created at run time, and your initialise procedure

foetusmachine · June 17, 2021, 8:24am

Is there an easy way to do this? There's over 50 including lists.

TIMAI2 · June 17, 2021, 8:25am

and these are all generated at run time ?

foetusmachine · June 17, 2021, 8:25am

Yes they are - many set to zero, but nonetheless set.

Anke · June 17, 2021, 8:41am

See here (point 3):

foetusmachine · June 17, 2021, 8:53am

Thanks @Anke. However, my real issue is that i don't want to share all of my code with the world.

I'll have to work through this myself I think.

foetusmachine · June 17, 2021, 9:08am

Okay, so i reverted to a much older code that I had at the front end:

This sort-of works - I still has the "Bad arguments to length of list" on the first load (new install), but if I click "Allow", then "End Application" and then reload the app, everything works fine.

Any ideas?

TIMAI2 · June 17, 2021, 9:10am

as previously indicated....

foetusmachine · June 17, 2021, 9:25am

Okay, I appreciate that, but i'm struggling to find the error.

I'm also wondering why after the first loading of the app, and I allow permissions, that the app works fine? Maybe that will give me a clue of where to look.

Anke · June 17, 2021, 9:41am

What is so difficult about posting the created variables / lists and the Screen.Initialize block before we have to continue puzzling out here.

foetusmachine · June 17, 2021, 11:57am

Let me organise the code and put the pieces together to share. Might take me a bit of time.

TIMAI2 · June 17, 2021, 9:18pm

If you remove everything from your Screen1.Initialise event, do you still get the bad arguments error ?
(Test with companion)

If you get no error, then put the blocks back, but then remove everything but the first item from your initialise procedure. If still no error add the second item, and so on.

If you get the error at some point, report back, or investigate.

foetusmachine · June 17, 2021, 9:22pm

Yes, I get the error with the Screen1.Initialise empty. Tested on phone.