Google Drive API behaviour for shared folders using the drive.file scope

Question

We have an application where we are trying to use the less sensitive drive.file scope but we are running into an issue: Say that there are 2 different users, User A, creates a folder from within our app (using the Drive API and the drive.file scope) and then shares that folder with User B also within our app using the permissions API. Then User B uploads a file to that shared folder (again, using our app with the same client id). The issue is that User A cannot see the files that User B has uploaded even though he has access to that folder (he created it) and the files were uploaded from our app (same app id / key).

From our understanding, when using the drive.file scope our app should be able to view the files created by our own app. In the example above the files are uploaded to a folder that both users have access to and they have been created via our app, why would User A don't see the new files when listing the contents of the folder?

Can someone at Google clarify this behaviour? I really hope this is a bug and can be fixed.

Thanks in advance for your help!