Allow meta data storage for Push Component #905
Comments
jrconlin
added a commit
that referenced
this issue
Apr 3, 2019
Push now stores `uaid` and the server secret `auth` in a table in the push.db. the meta_data table allows any key/value data to be stored to allow for additional future values (if needed). Closes #905
jrconlin
added a commit
that referenced
this issue
Apr 3, 2019
Push now stores `uaid` and the server secret `auth` in a table in the push.db. the meta_data table allows any key/value data to be stored to allow for additional future values (if needed). Closes #905
4 tasks
jrconlin
added a commit
that referenced
this issue
Apr 8, 2019
Push now stores uaid and the server secret auth in a table in the push.db. the meta_data table allows any key/value data to be stored to allow for additional future values (if needed). Closes #905
jrconlin
added a commit
that referenced
this issue
Apr 10, 2019
bug: store meta-data for push component in the database. Push now stores uaid and the server secret auth in a table in the push.db. the meta_data table allows any key/value data to be stored to allow for additional future values (if needed). Closes #905
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Push does not currently persist needed information across restarts (e.g. UAID, Server Auth token, etc.).
The text was updated successfully, but these errors were encountered: