ngageoint / mage-android

Mobile Awareness GEOINT Environment Android
Apache License 2.0
40 stars 22 forks source link

Body event id does not match #59

Closed vboulianne closed 1 year ago

vboulianne commented 1 year ago

While trying to input a new observation from cell phone, got the message "Body event ID does not match path event ID" Using MongoDB 4.4.14 (I tried 4.4.18 with same effect), Nodejs 14.21.2 (tried 16) on Ubuntu 20.04

Mage server 6.2.1, and Android version 7.1.7.

Web application works as expected.

Any suggestions you could provide would be appreciated.

Following is the term output:

2023-02-13T21:25:30.903Z - mongoose: users.find({ _id: { '$in': [ 63eaa1e1d1dbb981293af70e ] } }, { fields: {} }) 2023-02-13T21:25:30.904Z - mongoose: authentications.find({ _id: { '$in': [ 63eaa1e1d1dbb981293af70d ] } }, { fields: {} }) 2023-02-13T21:25:30.906Z - mongoose: roles.find({ _id: { '$in': [ 63eaa17dd1dbb981293af6ee ] } }, { fields: {} }) 2023-02-13T21:25:30.908Z - mongoose: events.findOne({ _id: 1 }, { fields: {} }) 2023-02-13T21:25:30.909Z - mongoose: events.findOne({ _id: 1 }, { fields: {} }) 2023-02-13T21:25:31.166Z - mongoose: tokens.findOne({ token: 'c9d030ce4028bcaeb7670bd1a49e0778bff8aacc' }, { fields: {} }) 2023-02-13T21:25:31.166Z - mongoose: users.find({ _id: { '$in': [ 63eaa1e1d1dbb981293af70e ] } }, { fields: {} }) 2023-02-13T21:25:31.167Z - mongoose: authentications.find({ _id: { '$in': [ 63eaa1e1d1dbb981293af70d ] } }, { fields: {} }) 2023-02-13T21:25:31.168Z - mongoose: roles.find({ _id: { '$in': [ 63eaa17dd1dbb981293af6ee ] } }, { fields: {} }) 2023-02-13T21:25:31.169Z - mongoose: events.findOne({ _id: 1 }, { fields: {} }) 2023-02-13T21:25:31.171Z - mongoose: events.findOne({ _id: 1 }, { fields: {} }) 2023-02-13T21:25:31.397Z - mongoose: tokens.findOne({ token: 'c9d030ce4028bcaeb7670bd1a49e0778bff8aacc' }, { fields: {} }) 2023-02-13T21:25:31.398Z - mongoose: users.find({ _id: { '$in': [ 63eaa1e1d1dbb981293af70e ] } }, { fields: {} }) 2023-02-13T21:25:31.399Z - mongoose: authentications.find({ _id: { '$in': [ 63eaa1e1d1dbb981293af70d ] } }, { fields: {} }) 2023-02-13T21:25:31.401Z - mongoose: roles.find({ _id: { '$in': [ 63eaa17dd1dbb981293af6ee ] } }, { fields: {} }) 2023-02-13T21:25:31.403Z - mongoose: events.findOne({ _id: 1 }, { fields: {} }) 2023-02-13T21:25:31.405Z - mongoose: events.findOne({ _id: 1 }, { fields: {} }) 2023-02-13T21:25:31.623Z - mongoose: tokens.findOne({ token: 'c9d030ce4028bcaeb7670bd1a49e0778bff8aacc' }, { fields: {} }) 2023-02-13T21:25:31.624Z - mongoose: users.find({ _id: { '$in': [ 63eaa1e1d1dbb981293af70e ] } }, { fields: {} }) 2023-02-13T21:25:31.625Z - mongoose: authentications.find({ _id: { '$in': [ 63eaa1e1d1dbb981293af70d ] } }, { fields: {} }) 2023-02-13T21:25:31.628Z - mongoose: roles.find({ _id: { '$in': [ 63eaa17dd1dbb981293af6ee ] } }, { fields: {} }) 2023-02-13T21:25:31.630Z - mongoose: events.findOne({ _id: 1 }, { fields: {} }) 2023-02-13T21:25:31.632Z - mongoose: events.findOne({ _id: 1 }, { fields: {} }) (and so on)

restjohn commented 1 year ago

That's a compatibility issue between MAGE Android < 7.2 and MAGE Server version 6.2.0+. MAGE Android 7.2 fixes the issue. While 7.2 is not yet in Google Play, you can test with the APK from the 7.2 release.

vboulianne commented 1 year ago

Thank you kindly for the swift answer.