They don't resolve that, but they do stop any people who have a libaccounts-qt Accounts::Manager instance from trying to instantiate a zero-id account due to the change signal.  But, while this helps clients of libaccounts-qt, it doesn't help clients of libaccounts-glib.

I'm of the opinion that we should just find a fix to libaccounts-glib's sync() implementation so that if an un-synced account is remove()ed and sync()ed, the operation is just a no-op (instead of the current explosive behaviour).