Need HELP with Mobile F7 app login process

[Teodor]

Check the browser console for errors please.

[sylvainbaron]

Hi Teodor,
The Console :

And the page:

Thanks

[Teodor]

Make sure you are using the latest version of the file Patrick already posted to you in one of your other topics:

Login form with F7 - nothing happend when submitting

Sorry it took a little longer, here a new update: dmxFramework7_6.zip (7.8 KB) There is no specific process for updating, just replace the existing file with updated one.

[sylvainbaron]

thanks @Teodor.
Just did it.
Once done do I need to accept the Update process?

[Teodor]

No, as this will replace the file with the old one.

[sylvainbaron]

this explain why i did not succeed previously… many thanks

[George]

@kfawcett

Awesome @George! Is this something that we will need to disable for production environments?

Just to explain here as well, by using the Capacitor Http module you are not disabling any security, just CORS checks - those are also not performed in your browser if you call the url directly.

All security provider and other restrictions stay in place.

So it is all save to be used in production as well.

[bpj]

Has anyone had issues with SC forms when enabling this plugin?

I get the following in Safari (using iOS Simulator) when submitting a SC form:
The first console error is when I submit the form using a Submit button for the first time. The second is if I click the same button again afterwards.

[bpj]

@sylvainbaron, @kfawcett,
Have either of you tried using a Server Connect form in Capacitor after the HTTP plugin was enabled?

If not, would you mind trying one to see if you get the same as me? I’d love to know if it is just my project or a wider compatibility with SC forms and the plugin.

@bpj

I get the following in Safari (using iOS Simulator) when submitting a SC form:
The first console error is when I submit the form using a Submit button for the first time. The second is if I click the same button again afterwards.

[George]

Well there might be a bug in the capacitor http plugin. See https://github.com/capacitor-community/http/issues/136

But we have also improved our CORS settings now, so giving origin of * or specific multiple mobile origins will work all fine. So you don’t really need the Capacitor http plugin any more.

[kfawcett]

@bpj

Have either of you tried using a Server Connect form in Capacitor after the HTTP plugin was enabled?

I haven’t noticed any errors on Chrome in Windows, Android, or Electron.

[bpj]

Thanks George and Keith,
I’ve had to switch to a different project but will have another try as soon as I can. From George’s link it looks like an IOS specific issue

[englandscott]

After adding the plugin now ios cookies works. However now the ios app is adding a ¶ to end of each line of a form field. This only happens with the ios version. The Android app is clean even though it is using the CapacitorHttp plugin. After researching I don’t see any mention of this issue on the Capacitor bug boards so I am wondering if it’s an implementation issue in Wappler.

[franse]

@englandscott what version of F7 are you using? App connect (stable or beta) is only compatible with 5.7.14

[englandscott]

FW7 Version 6.3.17

[franse]

Can you try with 5.7.14?
Make a backup first and remember to build after you change it

[englandscott]

No change.
FYI I am not using AppConnect 2.0 I am using 1.14.12

[franse]

The same as mine when I reported this:
https://community.wappler.io/t/framework-7-v5-7-14-no-longer-works/52127

If you add a f7 component, like action sheet, it will work on your chrome browser but not on android emulator or a released/debug apk.
The point I'm saying this is because I found unestable behavior with those f7 versions.

@englandscott

However now the ios app is adding a ¶ to end of each line of a form field.

Can you post some code/screenshot?