Sam Hulick

Hey Rob, We're at 1.2.1 now. I've commented out my bizarre error-handling code and will give this a try for a while to see if the issue is gone.

I was advised to retrieve the Cognito identity ID via `Auth.currentUserInfo()` and store it as an attribute in the user object in the user pool.

However, I can't figure out when the right time is to grab this info. Upon login, when I call `Auth.currentUserInfo()`, the `id` property is undefined. ```js async signIn({ commit },...

Ok, this works for me: ```js async signIn({ commit }, { username, password }) { const user = await Auth.signIn(username, password); const credentials = await Auth.currentCredentials(); console.log('Cognito identity ID:', credentials.identityId);...

`authenticate` isn't relevant here, just my own function that commits data to a Vuex store.

Totally agree. The SDK should handle these sorts of lower level operations for us.

@derekgreer Interesting no one noticed this, it's a great idea. When we squash our PRs on GitHub, it puts the squashed commits into the body, e.g.: ``` commit c18e83e1c45644ef7c81adae7fa7ed4581292b25 Author:...

@bcoe @stevemao Thoughts on this?

We've been running into this error lately, and the bad part is, it supercedes the _actual_ error we're trying to capture. So users are running into bugs in our app,...

@kamilogorek So, to continue showing that path from the code above: The object in the 3rd argument above gets passed into `reportError()` which starts like this: ```ts export default function...