Closed matt-allan closed 5 years ago
Sorry about this matt. I'm a bit confused to be honest. The PR that reverted the change didn't introduce any failing tests when reverting that change, so I believed the issue to be fixed by the adjustments made to hasEmbeddedEntities()
. However looking at the test file now, I don't see any record of the test that should've been brought in when your PR to resolve this issue was merged.
The fix is up again with https://github.com/helpscout/helpscout-api-php/pull/188
I'm still digging into this to try to find a solution so embedded entities that aren't collections aren't forced to be collections.
Can you provide me with the CustomerId you're running into this with? I've been testing on a pool of data on my end and can't seem to reproduce the same circumstances you're running into. Giving me this ID should allow me to reproduce it exactly.
Do you mean the ID of the HelpScout account or the customer ID I'm searching for?
If you mean the HelpScout customer ID I made a test OAuth app under my user ID 387237. If you use those credentials you should be able to reproduce the error. The same error occurs with our actual OAuth credentials but I don't know off hand the HelpScout customer ID of the account those are under.
The error seems to only happen when searching by email and no matching results are found, so as long as you don't have a user with the email 'matt.allan@somedomain.com' the reproduction script I posted in #175 should reproduce the error. Does it not reproduce the issue with the account you are using?
Thanks for that info, just what I needed! This is fixed in https://github.com/helpscout/helpscout-api-php/pull/189
Hello,
I previously reported an issue in #175, that was fixed by #176. #180 reverted #176 and it seems the issue I was experiencing originally is back. I tried updating to v2.3.9 and received the same error again:
The same reproduction script I included in #175 is able to reproduce the issue on master.