Parse File Error on back4app parse dashboard

[thwl]

When I click on an app image file on back4app parse dashboard, I get the following error:

AccessDeniedAccess Denied6FBE78C033173BF5eIl5zNYQcc00pxJ+...

It should open a webpage and show an image.

Is the error due to the file not being hosted on back4app?

Without the app files being migrated to back4app completely from Parse, do I still have to go back to the original Parse website dashboard to see my files?

When will the file migration solution be ready? Thank you :)

[Davi Macêdo]

Old files will keep hosted in parse.com servers while new files will be hosted in back4app servers. Parse is still working in a migration solution that shall be done until feb 2017. See more here: https://github.com/ParsePlatform/parse-server/wiki/Migrating-an-Existing-Parse-App#5-files

But the link should be available no matter if you are clicking in it though back4app dashboard or Parse one.

Have you deleted the app in parse.com after the migration? Could you please check if the link in parse is the same in back4app dashboard?

[thwl]

The file link that I clicked from back4app dashboard has this file url:

http://files.parsetfss.com/56bf7dcc-71aa-4ea7-92cc-82ea5c8c9510/tfss-7d13be6b-6283-4414-8c9f-ce652f8ecce1-9-Dec-2014%20Tue%202037h%20F43CB822-AB00-4B01-A0AB-E5CB14E32AB1.png

error: AccessDeniedAccess DeniedBAE0801F599C18CFiPyWF/FJIyFnF1vmvfpvt8C/dAOznIHN/ACUsXFBejzgw7X7Ez0/mBmjtmhpatwMuLwpWLqA6lM=

parse.com dashboard file url:

http://files.parsetfss.com/d1e0619d-4739-4a49-a8e2-b4c95f0ca809/tfss-7d13be6b-6283-4414-8c9f-ce652f8ecce1-9-Dec-2014%20Tue%202037h%20F43CB822-AB00-4B01-A0AB-E5CB14E32AB1.png

ok: image loaded

No, I did not delete my app from Parse.com since files are still hosted there and not fully migrated to back4app.

When will back4app provide a solution to migrate all parse.com hosted files to back4app?

[Davi Macêdo]

It is occurring because your filekey in back4app is different from the one in Parse. In back4app is set to 56bf7dcc-71aa-4ea7-92cc-82ea5c8c9510 while the real one in parse is d1e0619d-4739-4a49-a8e2-b4c95f0ca809. You have to update it in back4app to d1e0619d-4739-4a49-a8e2-b4c95f0ca809. You can do it by clicking in your app, then core settings, then edit. There you will see the filekey field. Update it and save.

About the migration solution we will wait little bit more for the solution of Parse. They don't have yet a deadline for it. But don't worry. If they don't provide the solution we will do it by ourselves.

[thwl]

Thank you for identifying the file key as the cause. The problem has been resolved.

Kindly develop the parse file migration solution without waiting for parse.com.

Thank you for doing a great job in helping us!

[Davi Macêdo]

You're welcome. Helping you, guys, is our mission!