-
-
Notifications
You must be signed in to change notification settings - Fork 274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS zmNinja sends token for platform Android #960
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you follow the issue template or I may not respond. |
Hmm this is the second time I've heard this. My android devices say android and ios says android. I deleted my tokens.txt file and re-registered my iOS device and see that it sends iOS. Can you do this:
|
Apparently zmNinja updated overnight because in the log it is now reporting Version 1.4.010. Here are the first log entries. It might be a bit confused because the mail button on the logs didn’t work, so I copy and pasted, which meant I switched apps a few times. Oddly, I see it registering initially as android, and then again as iOS (once). The current token file says android though.
|
Platform & OS Version
iPadOS 13.6
The version of zmNinja you are reporting:
1.3.010 (ios)
The version and OS of ZoneMinder you are using:
1.32.3, Ubuntu Focal Fossa (20.04.1 LTS)
Device details:
iPad Pro
What is the nature of your issue
Bug
(one of Bug, Enhancement, Question)
Details
Describe in detail. If its a bug, please describe what is happening, what should happen and how to reproduce if its not obvious
When I turn on the event server in zmNinja, it registers with the event server, but the token that is sent and recorded in the tokens.txt file says platform android instead of ios. I edited tokens.txt to change the platform to ios and the pushes worked, but it gets changed back when zmNinja connects.
zmNinja Debug Logs
(Sorry it's just one line, but I think it makes the point. )
Zoneminder Logs (if applicable)
Web Server Error Logs (if applicable, especially for streaming errors or API error)
Thanks!
The text was updated successfully, but these errors were encountered: