App will not connect to server when adding account

[ghost]

i have some issues with nextcloud sms, after trying the function reset pointer in the app, sync started to have issues with connecting to my server. i then tried to remove the account on my app and readd it, this is where the problem is, when readding the account i get a error message that the http:// server address is not reachable, i noticed that the error message says http:// is used eventhoug the app settings is set to https://
My server is not possible to reach with http at all, and if the app is ignoring the https:// ofcourse it would have issues connecting.

Would have been nice if you could fix this behavior

[nerzhul]

Can you provide screen shots and android app version ?

[ghost]

Iam sorry m8, its not possible to upload screenshots from mobile to github, so no images for you.

Anyway the problem persist, iam going to dump databse regarding to ocsms and try if the problem might be server related. But i doubt it as its connecttion issues

[ghost]

[ghost]

Any progress?

[roydenyates]

Can confirm CM13 (Android 6.0.1)
app ver 1.3.3.

I had it working and updated via f-Droid then saw notifications that the connection failed. However, if I opened app and manually synced there was no error. Yet the error notices persisted. Deleted account and here we are :-), no way back in.

PS: Nextcloud working just fine, so it seems to be an app error. Issue persists back to c 1.3.1. I think I upgraded from before 1.3.1.

[nerzhul]

it's a difficult issue to track in the new and mandatory HTTP client i need time to track this, it seems nobody has java/android skills to help fixing it :(

[nerzhul]

Also another fix has been pushed in 1.3.4 please re-test with it

[mourningsun75]

For me it is fixed

[nerzhul]

@mourningsun75 nice to hear

[roydenyates]

Confirmed - fixed in 1.3.4.

…

On 16 December 2017 at 10:33, Loïc Blot ***@***.***> wrote: @mourningsun75 <https://github.com/mourningsun75> nice to hear — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#170 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKXdbcCx8YHJa6IxpfjhxWK63GBT65Z-ks5tA45kgaJpZM4Q5OKT> .

-- Royden Yates Göteborg Sweden

[nerzhul]

@prilly can you confirm ?

[barti]

Hi, even when using 1.3.4 I can still see the same issue: when trying to connect to https server and connection fails, the error message says that the http:// server address is not reachable. I guess, in my case connection error is related to self signed certificate feature request 172.
Anyway, the error with hard-coded "http" as a string is misleading and confusing.

[nerzhul]

@barti exact i should fix the two issues. Sorry for the delay but i'm alone and there are rare PR on the app, and i'm working on many OSS projects :)

[JeromeSi]

Hi,
I've got the same problem in version 1.3.2, 1.3.3, 1.3.4.
With Android Studio, I make the apk with version 1.2.4 and this version work fine.
I've got lineageOS 14.1 (on a Moto G 4G, peregrine, android 7.1.2) with a nextcloud 11.0.6 and ocsms 1.11.4.
Thanks for the app.

[chrbayer]

Hi, it can not work with self signed certificates at the moment, it has to be allowed in the AndroidManifest.

in AndroidManifest.xml insert a new line after 37:android:allowBackup="true":
android:networkSecurityConfig="@xml/network_security_config"

and a new file res/xml/network_security_config.xml with his content:

This gives Android the permission to use self installed certificates, too :-)
Since the app crashes in my Emulator, I can not test, please someone with a working setup, make this small change :-)

And if it is working, I will purchase the app in the Store :-)

Best regards,
Christoph

[nerzhul]

@chrbayer thanks for the tip, but the network_security_config.xml has no content in your post :)

also i'm not sure it works with a golang library

[chrbayer]

@nerzhul This was the wrong issue, I wanted to insert my comment to #184, which I than did, and there is the missing file content :)

I'm not sure if it works for golang, too, but since it is some kind of safety feature, I would say, this permission should be independent from the used language...Nevertheless it is surely not wrong to tell the system that we want to use user certificates, so lose nothing in putting this in :)

[nerzhul]

such permissions depends on the underlying OS but the apk permissions are for android SDK, and we don't use the SDK for HTTP requests, but i can add the options at least as metadata for play store