1. Airship Support
  2. Community
  3. Engagement Platform - API

Could not parse request body. No configured device_types could be resolved from request.

Avatar
thompson sanjoto

I create a new airship project, a new app project with new bundle id.

followed https://docs.airship.com/platform/ios/getting-started/#apple-setup.

Uploaded all the Key file, keyID, teamID, and bundleID for the recommended token based auth

Install all the pods, and configure the configs on the app end. I can see the printed device token and the generated channel id.

I got a " Could not parse request body. No configured device_types could be resolved from request." when trying to send a message from the dashboard

need help

Didn't find what you were looking for?

New post

Comments

3 comments

Sort by Date Votes
  • Avatar
    eric.lannan

    Hello,

    There are 2 things that might be causing this. If it is your initial test, and the device you are using has not fully registered in our system you may get this error. The other issue is sometimes an app can get into this state and we have to escalate it so the platform recognizes your valid iOS configuration. 

    Since you have a ticket open with support, we can continue the app-specific questions and conversation there.

    Thank you,

    Eric L.
    Technical Support Engineer
    Airship Group | Apptimize | Portland

    Comment actions Permalink
    0
  • Avatar
    kiran

    Hi eric.lannan,

    I am facing the same issue within the dashboard. When I try to send a broadcast to only iOS devices, it is throwing an error, but not when Android Channel is also selected. But I could individually send a message to a selected channel that has an iOS device. Please help me sort this out. Thank you.

    Comment actions Permalink
    0
  • Avatar
    kiran

    I have discarded the whole iOS configuration and configured it again with a fresh key in Token-based Authentication,
    and it was working all good now.

    Earlier we have configured both token-based authentication and also certificate-based authentication, probably that certificate got expired or there was a conflict because of twos setups.

    I wish the error messages were self-explanatory.

    Thank you.

    Comment actions Permalink
    0

Please sign in to leave a comment.