Don't register ios users push notification ionic

After your update of .ts file the android users registration is ok iOs no i have no error message i get the token
Sans%20titre123

and i configured the server countly
image

0

Comments

12 comments
  • khalilbhs:

    and i configured the server countly

    Yes, I am working on it.

    0
    Comment actions Permalink
  • trinisofttechnologie:

    Yes, I am working on it.

    I have tested it again.

    You don't have to use FCM on iOS.

    Leave the config blank for 'GoogleService-Info.plist'
    and don't include GoogleService-Info.plist

    Remove the existing platform

    Re add it, and run it.

    0
    Comment actions Permalink
  • I had the same problem with ios even I realized the changes you asked me.

    here is the apn token:

    0
    Comment actions Permalink
  • Oh, so on iOS you are still facing an issue.

    This is not a good place for your issue.

    There are 3 - 4 questions on the forum.

    0
    Comment actions Permalink
  • trinisofttechnologie:

    There are 3 - 4 questions on the forum.

    Can you create a issue here:

    and I will look into it.

    0
    Comment actions Permalink
  • We can also get on a telco call / remote access and fix your problem on it.

    0
    Comment actions Permalink
  • I created the issue:

    0
    Comment actions Permalink
  • I had no answer for this issue 🙁🙁

    0
    Comment actions Permalink
  • I had this error message I do know if he can inpact the execution ??

    0
    Comment actions Permalink
  • the problem in this function add in the last update is not allowed by ios divice
    fonction
    fonction1
    which generated this authorization error

    0
    Comment actions Permalink
  • The server (that the POST request is sent to) needs to include the Access-Control-Allow-Headers header (etc) in its response . Putting them in your request from the client has no effect.

    This is because it is up to the server to specify that it accepts cross-origin requests (and that it permits the Content-Type request header, and so on) – the client cannot decide for itself that a given server should allow CORS.

    0
    Comment actions Permalink
  • khalilbhs:

    This is because it is up to the server to specify that it accepts cross-origin requests (and that it permits the Content-Type request header, and so on) – the client cannot decide for itself that a given server should allow CORS.

    @khalilbhs

    This is a known issue.

    Please create an issue on github, and I will fix this problem.

    Thanks

    0
    Comment actions Permalink

Please sign in to leave a comment.