Robby Helms

In our case, the problem was that we were doing `config.env = process.env`, which I suppose must have been overwriting some value that `@cypress/code-coverage` was setting. One way to fix...

@mtrezza Rewrote using async/await 👍 Happy to make any other adjustments. I also started trying to write a failing test in `Cloud-test.js`, but for some reason the `attributes` of my...

@mtrezza I finished creating the failing test for the `Cloud.run` case that @aforemny identified in #1347, so both of the identified cases now have failing tests. Is this enough info...

@mtrezza The most straightforward "solution" that comes to mind is simply disabling the Single Instance Controller. It seems to me that there may be a fundamental flaw in the Single...

@mtrezza In our case, we noticed that someone using our web app and mobile app at the same time could end up in a bad state. The web app was...

@mtrezza As an example of what I'm talking about, I just pushed a commit with all the unit tests passing where I call `ParseObject._clearAllState()` in `Cloud.run`, and `user._clearServerData()` in `User.logIn`....

@mtrezza It looks like clearing the data as I mentioned causes a couple twitter/facebook flows to fail in the integration tests. If you or anyone else has any suggestions for...

@mtrezza It turns out that disabling single instance mode has some pretty terrible side effects when it comes to how Parse updates the current user in local storage...so I think...

@aforemny @JohannWeging Did a PR ever get created for this issue? We ran into this same problem, although our case is for deleted fields being returned from `Parse.User.logIn()` rather than...

After some more investigation, I'm realizing that our particular issue will likely not be fixed by the proposed fix in `decode.js`. Our issue comes from [`Parse.User.logIn`](https://github.com/parse-community/Parse-SDK-JS/blob/alpha/src/ParseUser.js#L1077), which doesn't call `decode`...