app.StartApp

[theodore]

Hallo,

I habe moved from Android 10 to 13 and app.StartApp gives me a black

screen. Is it possible, I'm missing something, or does app.StartApp doesn't 

work with Android 13 anymore?

Theodore

[theodore]

I'm not on scoped. Even though I have Android 13 and a total

new installation of Droidscript. But this only workes until

Droidscript 191b2, what also is the last version, that allowed

to code a fully working file manager (file picker).

If you have Droidscript installed, completely deinstall first.

Install 191b2 and you'll get Droidscript folder in your average

sdcard without scoped.

I don't know, but maybe this can help the developer to find

a workaround to get Droidscript in the future being 

installed without scoped (hidden) storage.

[theodore]

Even a normal install of the latent Droidscript version to scoped

doesn't work for app.StartApp(). I have tested both ways.

app.StartApp is/was a powerful, important function.

[theodore]

It's possible, that an new installation of Droidscript to no scoped is possible 

until version 2.5, but I was/am to lazy to check it now.

[Alan Hendry]

HI,

As far as I recall if you installed DS (or other app) in Android 10 or earlier then it would be non-scoped storage, and upgraded versions of DS would be non-scoped. Otherwise Android will automatically enforce scoped storage. That means that all apps (including the Android Files app) are restricted in the folders they can use.

Regards, ah

[theodore]

Hi Alan, thank you for your answer.

I'll try to explain my problem little better:

  I'm using Droidscript since many years, used to be betatester and so I've came

over a few Droidscript versions.

From here: http://androidscript.org/beta/, you still get official versions.
191b2 used to be my favorite, because it is perfect for coding a wonderful 

filemanager with special functions for use with Droidscript, like viewing files, copy

and so on. You was able to also run any DS project outside of DS also and the

for example Copy it to the DS folder, to work on it again.

The DS companion, as I call it is something I use about every time, coding with

DS.

So now I upgraded to Android 13, where why ever, app.StartApp gives me

a black screen and forces DS to crash. So I've installed 191b2 on my new

phone, because this is the version I've written and compiled my file manager

with at first.

By accident now I've discovered, that this version is being installed to the

regular storage as before (no scoped) so I wanted to share this with the

development.

I'm using only official versions of DS.

So back to my problem.  All still work as usual inside my manager. Buy

app.StartApp doesn't work under Android 13 anymore.

How could I get this function to work again?

[theodore]

Of course I have first installed the last DS version, and only

installed 191b2 after that, for finding out, why app.StartApp 

isn't working anymore. 

This way I've came over the fact, that this older version even

on android 13 installes to the regular path of the phone.

[theodore]

The DS companion let's you by one touch Copy any project to the

DS folder, let's you move all projects around as desired. It is an app

that has become very important to me, because it completes DS for

use on phone extremely. If I get it to view my apps again, I can think

of, sharing it as an plug for everyone.

[theodore]

Running the app inside DS even let's you access scoped storage. As apk

not. 

I'm totally new to Android 13. What am I missing?

[theodore]

Posting here gives you many strange private answers also...???

Why is that so?

[theodore]

What is going on with DS?

[Symbroson]

You can turn off email notifications if that is what you are experiencing. If you get private emails from messages not posted online in the forum thats not standard procedure. If you are feeling offended in any way you are welcome to report those email adresses to the DS staff and appending the email content for context so that DS can take appropriate action. Otherwise I suggest politely asking to stop sending private messages to those users and if they keep messaging you and you feel annoyed, again, feel fre to report them

[theodore]

Thank you, Symbroson

[theodore]

@Symbroson

Since you've became part of the development of DS, could you help me with the problem

of app.StartApp() isn't working anymore?

[theodore]

I think, this could be usefull for everyone

[Oarabile Koore]

Also @Symbroson
I've been trying to contact the team via email about my CloudStore API key. Please help. Thanks. 

[theodore]

@Symbroson

I'd allow you privat message if you don't want to post official.

Greetings 

[theodore]

One quesbefore I try it, does the latest apkbuilder even work with former Droidscript versions?

[theodore]

One question, before is what autocorect messed up

[theodore]

@Symbroson

I'd of course would  share my code then also completely with you, privat

[theodore]

In hope, you'd keep it my copyright 

[wheelie tips]

we use the StartApp also and it didnt work for us, instead we use 'SendIntent', for example which opens the Samsung calendar:

let action = "android.intent.action.MAIN";
let uri = null;
let packageName = "com.samsung.android.calendar";
let className = null;
app.SendIntent(packageName,className,action,null,uri,null)

you can use Package Name Viewer 2.0 to find out the packageName of the app you want to start. 
Best,

WT