I did struggle with it for a couple of hours and after not having found the cause I just migrated to version 4.1. Having done that the error no longer appears. I know this is a rather radical solution but I didn't have the time to go into more detail. Hope that's an option in your case.
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community