Have more questions? Submit a request

3 Comments

  • 0
    Avatar
    Mike Dunn

    I know this is how it's supposed to happen, but what if it doesn't?  Where do I find help for that?

  • -1
    Avatar
    Fatih Turhan

    Mike,
    One potential reason for that could be that the player was already registered at another network. You may want to check out this article;

    https://support.brightsign.biz/hc/en-us/articles/1260802465009-The-serial-number-has-already-been-registered-error

    Another reason could be that the player could be running on an OS version below 8.0.119. This should be the behavior beyond v8.0.119, as that's minimum version that'll make a player compatible with BSN.Cloud/BrightAuthor:connected.

    Or it may have been configured before for some other type of setup, it could be for older BrightAuthor, for example. Prior configuration would have precendence in that case. What's described by the article should be the behavior out of the box, therefore you may want to factory reset any players that seem to be behaving in a different way. And ensure that they're running on an OS beyond v8.0.119.

    If the issue seems to continue please don't hesitate to send an email to support@brightsign.biz.

  • 0
    Avatar
    bobbybishop

    Mike,
    One potential reason for that could be that the player was already registered at another network. You may want to check out this article;

    https://support.brightsign.biz/hc/en-us/articles/1260802465009-The-serial-number-has-already-been-registered-error geometry dash lite

    Another reason could be that the player could be running on an OS version below 8.0.119. This should be the behavior beyond v8.0.119, as that's minimum version that'll make a player compatible with BSN.Cloud/BrightAuthor:connected.

    Thanks for your solution. It works for me

Please sign in to leave a comment.
Can't find what you're looking for? Try to
Powered by Zendesk