I built my an app with Ionic 5, The app is makes requests to an API which I made with Laravel 8, data is sent in json form while an API key is required and it is sent in the headers section.
Everything works fine when the App is built in debug version however the release version does not even give an indication of what's happening. For example the login button when pressed it does not do anything it only gives a timeout message which I had set in the app to let the user know the process failed.
The debug app works perfectly without any issues but the release app does not.
I'm sorry I can't post the entire code here since I can't pinpoint where the error seems to be coming from and it's a lot of code.
App - Ionic 5, Angular.
API - Laravel 8
Requests in JSON
Headers - API Key
I later checked the app logs on Android Studio logcat and this is the error that kept popping up: "E/chromium: [ERROR:ssl_client_socket_impl.cc(981)] handshake failed; returned -1, SSL error code 1, net_error -202"
Make sure that your server start with https and have a valid SSL certificate.
Related
I'm using Pusher for real chat application.
I've created a web app and a mobile app using Ionic 4.
The app use private channels, and everything works well on web enviroment.
During development i've tested the Ionic app on browser (ionic serve)
and the chat works very well.
When I tried to test the app on a real IOS Device (also XCode emulator),
i get an error in channel subscribtion
Unable to retrieve auth string from auth endpoint - received status 0 from https://...
I've tested the endpoint and works fine, even if I try to simulate the connection from the device as a simple API.
So I cannot understand where is the problem.
If I use a default channel (so no private) everything works fine also on IOS Device.
I'm thinking the problem should be on some Cordova/Ionic configuration?
Here's the code I use for Pusher setup and subscription (works if run on the browser with ionic)
this.pusher = new Pusher(this.environment.pusherKey, {
cluster: 'eu',
encrypted: true,
authEndpoint: this.mainService.hostEndpoint + 'user/pusherAuth',
});
this.pusher.subscribe(channelName)
Who's the hero who can help me solve this problem? :)
I don't want to rollback on the not a private channel just as a workaround for the problem.
for me i had the same issue and fixed that with adding 'Access-Control-Allow-Origin' header to my server response.
I can run the app in the browser after clearing data, but if I then add it to the homescreen and attempt to relaunch from there, I get a plain page giving the following error:
Safari cannot open the page. The error was: "FetchEvent.respondWith received an error: Returned response is null."
Subsequent launches in the browser then also give that error. I have to again 'clear data' in the browser to get it to work again.
I'm using Workbox v3.6.2 (the latest, at the time of writing), and my iPhone is running iOS 12.
This looks suspicious, but it's a bit over my head (well, the workaround is anyway). It makes me want to try to down grade to iOS11.X again, and/or install Technology Preview 59.
I have this same problems. On iOS 12.0.0 work properly but after updating to version 12.0.1 I have this same error like you. I have test this same application but on two different devices (iPhone) with two different version of iOS.
Looks like there are multiple possible reasons for this error - I've had it twice ;
Occasion 1 : Needed to add a ROOT certificate and set it as Trusted on device.
my conditions;
I was getting the same error on an iPhone 5s with iOS 12 when loading pwapp from local server.
Using self signed certs on a development machine for server.
Not using Workbox.
Not getting problem if loading pwapp from provider hosted server with ssl cert from iOS recognised cert authority.
Turned out it was to do with security certs - (not using a mac so can't debug to the level of network/security issues on the device / direct to fully diagnose).
Fix was to ;
create a self signed root cert and use that for my server.
convert (copy of) root cert .pem file to .der
access .der via safari on the device / add profile, set as trusted.
(Correct way is to do root, intermediary and server certs , use the server cert and serve the root cert via url or email it to email client on device.)
useful links ;
see Getting cert in General->About->Certificate Trust Settings
Occasion 2 : Turns out you have to access the pwapp from the home screen icon at least once while you have access to the server.
To reproduce ;
(networking on)
delete icon from home screen and clear safari history and website data
visit the pwapp url
add to home screen but do not launch
turn off networking
attempt launch from home screen => get the error
turn on networking, launch pwapp from home screen => ok.
close pwapp, turn off networking, launch pwapp from home screen => ok.
So looks like an iOS/Safari/Webkit bug
Everyone I am using vidyo library in android. I am able to see preview but not able to connect to api. Anyone can help me. I generate token with cmd in Windows. There is any problem with vidyo library versions. Please Tell me which version work for Android 6.0.
Can you copy paste the error messages shown on the console?
The most common error during connecting is an invalid token. Double check if the token is valid. to test you can create a token on this helper website - https://vidyocreatetoken.appspot.com/
Note, in your username do not include any special characters (especially '#'). And get your developer key and app Id from the vidyo dashboard - https://developer.vidyo.io/dashboard
I am trying to setup Firebase in my Nativescript app(Angular 2- TypeScript). However, It prompts me the error as below.
A valid Facebook app id must be set in the AndroidManifest.xml or set by calling Facebook.setApplicationId before Initializing the sdk.
Why should I provide the Facebook app ID for the start-up?
Any idea?
Much appreciate.
I have resolved by reinstalling the native-script-firebase-plugin without initialized the Facebook's Authentication for this error message "A valid Facebook app id must be set in the AndroidManifest.xml or set by calling Facebook.setApplicationId before Initializing the SDK"
As for the second error message "Google Play Service is required on this device", I just installed and upgraded the Google Play Service on the particular Android Emulator, and it works fine now.
In conclusion, is worth to check the Google Play Service it has been installed and upgraded to the appropriate version or not.
I have a JIRA REST API endpoint I want to make a call out to. From the Windows POSTMAN app I get the following error:
There was an error connecting to https://jiraurl.com/rest/api/2/issue/a123.
However if I use the Chrome app POSTMAN same URL it works just fine. With the chrome app i can make the request without any headers and i get a response. With the Windows app I've tried several different auth headers without any luck.
I'm assuming it has something to do with certs or the fact that in chrome i'm already logged in to the JIRA instance and so no further authorization is required I just can't figure out what settings or headers i could be missing.
The reason why I'm trying to figure out if the windows app is because i'm writing a c# program and i'm getting the same error so i know it's not necessarily a POSTMAN issue.