I suppose you're not using your admin account but API username and password, right?

They must be translateable, going to ask this to our mobile guys and then add to Crowdin by tomorrow

Since it's standing just Username, and not API Username, I assume it's the regular username that should be use.
Anyhow, didn't find any docs or descriptions. The dedicated page is quite empty too: https://arastta.org/mobile

Agree, it must be API Username but you know, there is no username for admin account in Arastta

Docs and more will come, we're just starting the game

Users don't see the difference.

Anyhow. User credentials doesn't give any feedback about it being wrong, and API credentials is declined as wrong.
Is it only the default API credentials (#1) being accepted?

Issue created: https://github.com/arastta/android/issues/1

No, there is no restriction for credentials usage.

OK, sent you a PM with test info.

Tried it a month or so ago, and asked here in the forum for support.
It's isn't working. Doesn't connect from what I could see.

Try this one Breck https://arastta.org/mobile

Problem right now is that after I restarted the demo site, I noticed there are 4 instances of the module. 3 are disabled and 1 enabled.
Trying to open and edit them, most keep coming up as permission denied. Even though I have granted permission in the administrator group. I deleted the disabled ones, and tried again and no access. I deleted all of the and installed the 1.0.0 version from the marketplace, and I can edit it, but it won't enable after saving. I think that was my problem and question before. How do you enable it if it refuses to enable.

So this is kind of weird. I cleared the cache, and now 3 mobile assistants appear again.

Mobile Assistant - CsShop - 1.0.0 - disabled - permission denied
Mobile Assistant - Arastta - 1.0.0 - enabled - permission denied
Mobile Assistant - Arastta - 1.0.0 - disabled - accessible - won't enable

Not sure what to do at this point.

There is no module for this one Breck, you are confusing this withe other third party version. This tread is not about the Mobile Assistant from eMagicOne.

If you are going to use the latest Mobile App from Arastta linked to by Denis, which this tread is about, you can just remove those instances - or do a new demo site if you have messed up the old one. Else it would be better to start a new tread about Mobile Assistant from eMagicOne, or even better, contact the eMagicOne support.

ok got it now. Sorry for the confusion.

ok some new questions.

I created a mobile api login, and not sure, do we use the store url or the admin url?
Trying both and getting connection failed each time.

Will continue to play with it and hopefully I can figure it out.

Rune Rasmussen wrote:
On thing quite a few does, is not paying attention to the texts on the screen.
Some write full admin url, including http/https, when it should be only store url without http/https and admin.

So ... domain.com or www.domain.com ...

Still connection failed.

Rune Rasmussen wrote:

By the way, my problem connecting was this one: https://github.com/arastta/arastta/issues/573
Had debug display active at the test site.

Did you read this then?

Don't think it's that. I can access api settings. And I don't know where to enable debug so unless it was enabled on install, it should be off.

Don't just assume please, but check it, a make yourself familiar with the settings in the store: https://arastta.org/docs/user-manual/system/settings/server

It is disabled.

Then you most likely are typing something wrong, post a screen of the exact error. Anyhow, you must post more info.
PS! If you selected TLS, try not using it.