Parse File migration question.

[ssamkyu]

After migration, I checked ParseFile Url in back4app parse dashboard. then I found out that the file url is same as saved in "Parse".

It is understood for me that ParseFile is still save in "Parse" not "Back4app"

I wonder "back4app" migration migrate the file to back4app's server or just save the file url saved in "Parse".

What I really want to know is that after shutting down "Parse", the files which is mirgrateed from "Parse" to "back4app" can survive or not.

I am not familiar with "Parse-Server". so the question could be look funny. but it seems important for me.

thanks.

[Davi Macêdo]

It is really a very good question!

In the parse.com dashboard migration process, they don't migrate the files (https://github.com/ParsePlatform/parse-server/wiki/Migrating-an-Existing-Parse-App#5-files). So, existing files will be still stored in parse.com servers, and only the new files will be stored in the back4app.com servers. Since you have correctly set your file key, it will work fine.

BUT it will work only until jan/2017. So until there you will have to migrate your files from parse.com servers to back4app.com servers. Parse has not yet delivered any solution for it, but they claim they have a plan: https://github.com/ParsePlatform/parse-server/wiki/Files-Migration

Don't worry. Being with us, no matter if Parse will deliver the planned tools or not, we will provide you the solution for it in the following weeks.

[mybi...@gmail.com]

Is it possible to use back4app server and host larger photo files with AWS S3?

[Davi Macêdo]

I will ask you to wait few weeks. We will start storing all files in S3.

[herna...@gmail.com]

Hi:

I'm failing to Download the Purchased IAP's in My App. Is this the Cause of this Problem?

So If I Understand All the Data has been Migrated but the Files are Still at Parse and Since My App is Pointing Now to Back4App Downloads are Failing?

If this is the Case, How can we Fix this?

Thanks

Hernan

[Davi Macêdo]

Hi, Hernan. Besides files are still in Parse, it should work fine. Could you please paste here the error you have?

[Hernan Arber]

Hi Davi:

Thanks so much for the Help:

The error I'm Getting is:

[Error]: The request timed out. (Code: 100, Version: 1.12.0)

then I Sometimes get:

2016-04-15 02:44:54.836 Loopacks[253:36733] [Error]: The request timed out. (Code: 100, Version: 1.12.0)

2016-04-15 02:44:54.839 Loopacks[253:36733] [Error]: Network connection failed. Making attempt 1 after sleeping for 1.545312 seconds.

But the Network is working FINE, the proof is that I'm able to get the Data for my products from you DB @ Back4App.

What might be the Issue here?

Thanks

[Hernan Arber]

Hi Davi:

Adding to that, this is an Example of my File entries @ the DB:

{"__type":"File","name":"tfss-82131de0-bebb-45e1-be80-120f2cdfaaa0-JungleTerror.zip","url":"http://files.parsetfss.com/ed853598-f408-494e-93de-984b5a496c16/tfss-82131de0-bebb-45e1-be80-120f2cdfaaa0-JungleTerror.zip"}

The URL Works and I Can Download the File:

http://files.parsetfss.com/ed853598-f408-494e-93de-984b5a496c16/tfss-82131de0-bebb-45e1-be80-120f2cdfaaa0-JungleTerror.zip

But I Can't do this within the APP. What can be the Issue?

Thanks

Hernan

[Hernan Arber]

Here is my Code for Buying a Pack:

- (void) buySelectedPack

{

//    [self addObserverForPack:self.currentPack];

    if(!self.pfPurchaseInProgress)

    {

        self.pfPurchaseInProgress = YES;

        // adding the Purchase Observer

        [PFPurchase addObserverForProduct:self.currentPack.packProductID block:^(SKPaymentTransaction *transaction) {

            [PFPurchase downloadAssetForTransaction:transaction completion:^(NSString *filePath, NSError *error) {

                if (!error) {

                    // Unzipping

                    NSString *documentsFolder = [NSSearchPathForDirectoriesInDomains(NSDocumentDirectory,

                                                                                     NSUserDomainMask,

                                                                                     YES) lastObject];

                    NSString *packsFolder = [documentsFolder stringByAppendingPathComponent:LS_LOOPACKS_SUBDIRECTORY];

                    

                    if([SSZipArchive unzipFileAtPath:filePath toDestination:packsFolder]) {

                        //unzip data success

                        //do something

                        LSLog(@"SSZipArchive unzipFileAtPath Success");

                        // Adding the Pack:

                        NSString *fileName = [filePath lastPathComponent];

                        NSArray* onlyFolder = [fileName componentsSeparatedByString:@"-"];

                        NSString* zipFile = [onlyFolder lastObject];

                        NSString* subFolder = [zipFile stringByDeletingPathExtension];

                        LSSoundPack* newPack = [[LSSoundPack alloc] init];

                        newPack.packFilePath = [packsFolder stringByAppendingPathComponent:subFolder];

                        if([newPack loadPackWithPath])

                        {

                            [[LSSamplePackManager sharedPackManager] addPackToApp:newPack];

                            NSDictionary* dict = [NSDictionary dictionaryWithObject:newPack forKey:@"packToLoad"];

                            [[NSNotificationCenter defaultCenter]

                             postNotificationName:@"LoadNewPack"

                             object:nil

                             userInfo:dict];

                        }else

                        {

                            [[LSSamplePackManager sharedPackManager] loadAllPacks:YES];

                        }

                        [SVProgressHUD showSuccessWithStatus:@"Enjoy your New LooPack :-D"];

                        // for the NON-ICLOUD-BACKUP

                        [self addSkipBackupAttributeToDirectoryAtPath:packsFolder];

                        // parse Tracking:

                        [self reportSale:self.currentPack.packName];

                        // Deleting the ZIP File:

                        NSFileManager *fileManager = [NSFileManager defaultManager];

                        [fileManager removeItemAtPath:filePath error:nil];

                        

                    }else{

                        LSLog(@"SSZipArchive  unzipFileAtPath Error");

                        [SVProgressHUD showErrorWithStatus:@"Please Re-Download the Pack...)"];

                    }

                    [self.packCollectionView reloadData];

                }else

                {

                    [SVProgressHUD showErrorWithStatus:@"Error"];

                    [self reportSaleError:self.currentPack.packName];

                }

                self.pfPurchaseInProgress = NO;

            }];

        }];

        

        [PFPurchase buyProduct:self.currentPack.packProductID  block:^(NSError *error) {

            if (!error) {

                // run UI logic that informs user the product has been purchased, such as displaying an alert view.

                [SVProgressHUD showWithStatus:@"Downloading..."];

            }else

            {

                LSLog(@"ERROR Buying Pack: %@", error);

                [SVProgressHUD showErrorWithStatus:@"Error"];

            }

        }];

    }

}

[Hernan Arber]

Davi: Are you therE?

I Need your Help bro. I Just got a NEW Error after Waiting for the Download Connection to Time-Out:

Error Domain=NSCocoaErrorDomain Code=3840 "JSON text did not start with array or object and option to allow fragments not set." UserInfo={NSDebugDescription=JSON text did not start with array or object and option to allow fragments not set.}

Does this say anything to you?

Thanks

[Davi Macêdo]

Hi, Hernan. Can you observe in your parse.com dashboard if the file protocol is also http:// ? I think that it should be https and it can be causing the failure. Same code is working fine when connecting to api.parse.com? Best!

[Hernan Arber]

Hi Davi:

How / Where can I See regarding the https Protocol? 

And YES, Exact Same code is Downloading the Files OK when Pointing to the Original Parse Server instead of https://parseapi.back4app.com

How can I Fix This?  Maybe this is just a Matter of catching the File Address and Adding an "s" o the http?

Thanks....

[Hernan Arber]

I see that the address of the file is http:

http://files.parsetfss.com/ed853598-f408-494e-93de-984b5a496c16/tfss-82131de0-bebb-45e1-be80-120f2cdfaaa0-JungleTerror.zip

You can even test the link to check that FIles are actually downloading...

But how can I Change this without Re-Uploading the File? and if needed, how can I upload the FIle Again using the Parse Dashboard? Is there a way to support regular http: for Downloads?

Thanks

[Davi Macêdo]

Hi, Hernan. I really checked in details all code of Parse Server and iOS SDK related to PFPurchase and downloadAssetForTransaction:transaction. It seems to be a bug in Parse Server. PFPurchase support was not initially open sourced by parse.com and later it was developed by the community. But I can see that was not so much tested and few people had used it until now. I couldn't find any people using downloadAssetForTransaction.

Anyway, I can help you. But I will have to identify the exactly line of code that is generating the error inside the Parse iOS SDK Library. So I can check what is missing in Parse Server and post a solution to the community. By this way, would it be possible you send me the complete stack trace of the error you have? Please, send me everything that is logging in your console.

Meanwhile you can use regular download classes to allow your customers download the files after the transaction:

https://parse.com/docs/osx/guide#files

Best!

[Hernan Arber]

Hi Davi:

Unfortunately, all I Got is the Error's INFO:

Error Domain=NSCocoaErrorDomain Code=3840 "JSON text did not start with array or object and option to allow fragments not set." UserInfo={NSDebugDescription=JSON text did not start with array or object and option to allow fragments not set.}

How can I Turn the VERBOSE Level for Parse?

I'm going to Check out the Link you sent me for Downloading Files, Maybe that is the Key... Thanks

[Hernan Arber]

And now This Error is Back:

Error Domain=SKErrorDomain Code=0 "Cannot connect to iTunes Store" UserInfo={NSLocalizedDescription=Cannot connect to iTunes Store}

:-S I'm going crazy here... plz HELP :-d

[Davi Macêdo]

Hi, Hernan. We published some improvements in our server yesterday that can solve your issue (I am nor sure). Can you please try again?

[Hernan Arber]

Hi Davi:

Well, Unfortunately the Same code for the Download  was Failing, but the NEW Way of downloading DID work... No I Have a Different Problem:

Error Domain=SKErrorDomain Code=0 "Cannot connect to iTunes Store" UserInfo={NSLocalizedDescription=Cannot connect to iTunes Store}

2016-04-30 19:19:01.480 Loopacks[326:27890] Apps

I Think this is corrected when I Enter the Password Manually instead of the TouchID... What can be causing this?

OK I'm glad I Got the Store to work. Will keep you posted...

:-)

[Davi Macêdo]

Hi, Hernan. I am happy you have it working by using the other approach. About the "Cannot connect to iTunes Store" erro, it does not seem to be a problem related Parse Server, because Parse SDK for iOS connects directly to the iTunes Store without passing through server. So, it's an implementation problem or a bug in Parse SDK.

I looked for it and found the links below that can help you:

https://parse.com/questions/iap

http://stackoverflow.com/questions/30041106/in-app-purchase-cannot-connect-to-itunes-store

It seems that you cannot test purchase from simulator, but only through real devices.

If you need any assistance, let me know.

[Hernan Arber]

Hi Davi:

I've sent a TestFlight Version to Check for In App Purchases and Restoring with the New Implementation. I Hope Everything is working alright.

All and All Back4App seems to be working great, and I Hope you guys get all parse Features online soon.

I have to say, I went through a LOT of Parse Alternative, and you can quote me on this one:

The most important improvement I see in Back4App is your Personal Attention DAVI, and I Think it makes all the Difference. 

I'll keep you posted, I'll need Help for Adding new Files to the Products Table, this is also an issue on the Original PARSE Dashboard, but I'll open a new Topic for this.

Cheers

Hernan

[Davi Macêdo]

Hi, Hernan.

Thank you very much. For sure we will quote you :)

It is pretty rush here but we are doing our best to help Parse Lovers to keep their apps running.

Best!

[Fatih Cankurt]

Hi.

 I want to ask a question. I just start to develop android application and i will need login. Cani use this service without parse.com or how can i sign up to parse ? Thx for help

[Davi Macêdo]

Hi, Fatih. Sure. We use same technology of parse.com but our service is completely independent. It is now an easy task to replicate parse in few months but we are doing our best to make back4app the best alternative to parse lovers. In order to use our services, you are not required to be signed in parse. Best!

[ab.sa...@gmail.com]

Good question....really I also want to know the same thing...

My client still waiting for there solution...

Please advise!

[Davi Macêdo]

Hi, do you need more information than the ones provided above? Best!

[ab.sa...@gmail.com]

Yes.. I want to migrate & finalize the migration my app to back4app...

According to your suggestion, my app can read images from parse server[by file key change].

when back4app provides the file migration tool?

If the tool provided then we can migrate the file from parse to back4app server and file can be accessable as now right.

Please advise ...

Thanks

Sarfaraj 

[Davi Macêdo]

Yes. If you set correct file key, things will already work fine now.

We are already working on files migration tool that should be available in the following weeks. After files migration, all files will be in back4app servers and this will keep working fine.

[michae...@qwal-it.com]

Hi Davi,

I'm also in the process of migrating my parse server and database to back4app and I'm facing the same issue the the migration of the images files.
I've changed the file key in back4app settings in order to make the already existing image files hosted on parse server accessible, this is working.

But, can I Finalize the migration process on parse side ? How will I be able to migrate the existing images hosted on parse server to the back4app server ?
Or, do I need to wait that the images are migrated/hosted on the back4app server before finalizing the migration process in Parse ?

Regards.

Michael

[Davi Macêdo]

Hi, Michael.

You have to finalize the migration process. Otherwise parse.com will not start connecting to back4app database.

Images will be migrated from parse later using another specific feature that community is developing (we are already working on it together with Parse Server team).

Best!

[ins...@gmail.com]

Hey Michael,

I just heard about https://mv.sashido.io I've migrated my files and everything looks great.

The numbers at the top of the page are real. I saw my numbers there!

Hope Davi and his team will be release something like this soon.

Cheers,

- Ina

[Davi Macêdo]

Hi, Guys.

Open source community is delivering in the following days the official tool and we will give instructions to everybody in order to migrate the files. It will be as simple as click in a button.

I recommend you wait for it, but anyway if someone wants to use this tool, just reach us through web-site chat and we will give you the required information.

It is importante you observe that before migrating the files your app should be already connecting to back4app.com api, because parse.com api is not able to find files that is in other S3 bucket. Therefore, if you migrate the files before updating your api, your clients will fail to download the files.

Best.

[skala...@gmail.com]

Davi,

Any update on this? This is stopping us from migrating to back4app. 

Cheers,

Tomasz

[Davi Macêdo]

Hi, Tomasz.

It will be available in next upate. But why is it stopping you from migrating?

best!

[Tomasz Zablocki]

When do you plan to release new update?

Cheers

[bb...@mtu.edu]

Are you saying the files will be removed from Parse's hosting? (Meaning any users of the app that still point to parse.com will not be able to retrieve files...?)

When you "recommend [we] wait for it", is there any harm in migrating the app in the traditional sense and doing the file migration with the new tool at a later date? Consequently, is there any issue with waiting for the initial migration until your file-migration tool is ready as well?

[bb...@mtu.edu]

Davi, I'd appreciate a response (said without malice, I understand things get busy). Thank you.

[bb...@mtu.edu]

Still waiting on a response... see message dated August 3 below.

[Davi Macêdo]

Hi, Brendan.

Sorry about the delay. Things were pretty rush here in the past two weeks, because we are working hard to upgrade software and servers to better handle your requests.

Let me explain to you (and all others) everything about files.

Firs of all, I'd like to explain the migration process. As you know, in the parse.com -> back4app.com migration process, parse.com migration tool moves the database previously on parse.com servers to a new database on back4app.com servers. Parse.com API and dashboard start connecting to this new recent migrated database inside Back4app servers. So, after confirming the migration, both back4app.com api, back4app.com dashboard, parse.com api and parse.com dashboard will be running fine, synced and smoothly because actually they are all using the same database inside back4app.com servers. In the next step, is expected you update your app to make it connect to https://parseapi.back4app.com/ api, instead of https://api.parse.com/1/ one, (take a look here: http://docs.back4app.com/docs/parse-migration/parse-sdk/) and publish the new version of your app. Then your customers will start updating their apps in their devices. The ones that have already updated the apps, will be connecting to back4app.com api but the ones that have not yet updated the apps, will continue connecting to parse.com api (It is ok, because, as I said before, both will be connecting to the same database).

Now talking about files. When you use parse.com migration tool, your existing files are not migrated and keep stored in parse.com S3 bucket. At the same time, you will have files being uploaded through back4app.com API and being stored in back4app.com S3 bucket but you will also have files being uploaded through parse.com API and being stored in parse.com S3 bucket. Summarizing, you will have three "kinds" of files:

1) Your existing ones in parse.com S3 bucket;

2) Your new ones uploaded by the users that have already updated their apps, through back4app.com API and being stored in back4app.com S3 bucket;

3) Your new ones uploaded by the users that not have yet updated their apps, through parse.com API and being stored in parse.com S3 bucket.

The problem is:

1) Back4app.com dashboard and API are able to handle files that are in back4app.com S3 bucket and also the ones that are in parse.com S3 bucket;

2) But parse.com dashboard and API are only able to handle files that are in parse.com S3 bucket and not the ones that are in back4app.com S3 bucket.

Therefore, if you move your files now from parse.com S3 bucket to back4app.com S3 bucket, your customers that have not yet updated their apps, will not be able to see the existing files.

And what is the recommendation? First of all, migrate the database, update the app and publish it in the app store. Second, wait for your customers update their apps. And finally after all your customers updating their apps, migrate those files.

How will the migration of files be done? We will provide you in the following days a tool in our dashboard in which you will be able to start the migration process. This tool basically will use this open source project here developed by the Parse Server community: https://github.com/parse-server-modules/parse-files-utils

If anyone wants to migrate the files himself now using this tool (or any other tool), just reach us here in the web-site chat. We will give you your AWS S3 bucket credentials or any other information you need.

You can trust on us. We know what we are doing and everything will be sorted during parse.com sunset. :)

If you have any other question, let me know.

Best!

[quynhng...@gmail.com]

Hey Davi, 

Any update on the file migration tools? Thanks!

[Davi Macêdo]

Hi.

Thank you for following up. Migration tool is under tests right now and will be available in the following days.

Best!

[rattu Singh]

Hey Davi Macêdo,

I am facing same concern but I don't have any purchase integration.
    

I just migration my App data from Parse to Back4App and followed the steps to set up back4App configuration. But now when I hit the Parse API with reference to back4App. It is continuously giving me following error: [Error]: The certificate for this server is invalid. You might be connecting to a server that is pretending to be “files.parsetfss.com” which could put your confidential information at risk. (Code: 100, Version: 1.14.2) Error]: Network connection failed. Making attempt 1 after sleeping for 1.171176 seconds. Can anyone please provide a solution for this kind of error. I have updated Parse SDK in my App as well as ParseFacebook SDK.

Thanks in advance.

Thanks,
Rattu

   

[Davi Macêdo]

Hi, Rattu.

Can you please paste here the query you are performing and is throwing this error?

Best.

[tomasz....@pixle.pl]

Davi,

Any update on this???

[Davi Macêdo]

Hi, Guys. Yes. We have.

File migration is now available in our dashboard. Sign in back4app -> click in your app -> File Migration

Let me know if you need any help.

Best!

[andrey...@gmail.com]

Hi Davi!

We tried your file migration and noticed a really interesting bug - migrated files are losing first symbol in their names. I don't believe this is intended. Please advise. Thank you.

[Davi Macêdo]

Hi, Andrey.

Could you please send me your app id and the url of a file with the problem to ad...@back4app.com?

Is this file loading though?

Best!

[andrey...@gmail.com]

Hi Davi!

My test application id is qGd81w6HjoBLId3dHqEyn6SIuE5wrQ9ZkYy5Tr9J

All my filenames were truncated in the dashboard after file migration. Links work good, but in the dashboard all looks not good.

For example we have file (Core->Browser->Packs->Line UsmGszHoCw, thumbnail column) that looks like humbnail.png and it was thumbnail.png before migration. All other filenames lost first letter too.

We have tested it again on the small test project with only one file and all looks good before we call file migration in back4app. But first letter disappears after migrating files. Links still work and we have access to these files from the code. It seams all looks good in the link (https://parsefiles.back4app.com/qGd81w6HjoBLId3dHqEyn6SIuE5wrQ9ZkYy5Tr9J/mfp_799edfb74c8ed4651f690fef46083e42thumbnail.png) but this is the problem when we need to manage a lot of files in the dashboard.

Thanks!

[Davi Macêdo]

Hi, Andrey.

Got it and just checked your app here.

Actually the file migration tool did not change your file names. This is a bug in the open source dashboard that hide some letters of the filename. The filenames are correct like before the migration though (you can check it by getting some file from API).

We will work to solve this bug and update the dashboard.

Best!

[david....@gmail.com]

I am finding that files uploaded with longer file names are missing the first word in the dashboard.  When PFfile getdata gets called, I get- [Error]: unsupported URL (Code: 100, Version: 1.14.2).

[Davi Macêdo]

Hi, David. The dashboard has a known issue of cutting some letters of the file name. It will be addressed soon, but you file name keeps intact though. The unsupported URL probably is related to another issue. Can you please send me to admin@back4app your app id the url of a file that you can't load?

Best!

[mybi...@gmail.com]

Davi, I am having more difficulties downloading PFFiles for my app zgqRRfY6Tr5ICfdPocRLZG8EXK59vfS5dpDM5bqr

For the object PFTour, most of the new gpxFile's give me a network timeout and unsupported URL error with iOS.  I am able to download them in the dashboard.  Please email me if you are able to help troubleshoot. Thanks.

[Davi Macêdo]

Yes. I can help you to troubleshoot it. Please pick up a time slot in the link below.

https://calendly.com/back4app/15min/12-15-2016

Best!

[David]

I have migrated database from parse to back4app and created new version of our app that talks to back4app api instead of parse api. Now I have to submit app to apple store and release it before parse shut down. Our plan is to release it on Jan 22,2016 before parse shutdown so that all customers will have to switch to new version (back4app one) after Jan. 28, 2017 because old app with parse api will stop working. Now my plan is to migrate files (image PFFiles) from parse to back4app on 22 Jan. so that all images that exist on parse will be moved to back4app.

Now I have few question regarding file migration

1. After 22 Jan, our back4app api users will be able to access their images that they have uploaded on parse earlier because of file migration. Is that right?

2. After 22 Jan., our old parse api users can use old app between Jan 22 and Jan 28. If they upload new images then those images will also be saved on back4app because of file migration. Is that true? if not, can I move all images (that will be uploaded between Jan 22 and Jan 28) from parse to back4app using file migration feature on back4app? OR file migration can be performed only once.

3.How long does it take in file migration? Does it take more than 1 day? I am releasing app on Jan 22 so that if I get issues during file migration then I will have at least 6 days time for fixing those issues. I can release it on Jan 27 but in that case I will not be able to migrate files from parse after Jan 28 if I get any issues and file migration fails.

4. Is it necessary to migrate files only after all users have updated old app with new version? I think that is not a good idea. If we release our new app on Dec. 22,2017 instead of Jan 22, 2017 then it is possible that some users will not update app before 28th Jan. then we will have some users on Parse and some on back4app. But if we release it on 22 Jan then all users will be forced to download new version after 28th Jan. and we will have to deal with only 6 days files that can be uploaded by users between Jan 22 and Jan 28. Please let me know if you see any major drawback in this approach. What is the worst thing that can happen if we use this approach.

Thanks in advance.

[Davi Macêdo]

Hi, David.

Ricardo told me your questions were answered in the chat today, right?

Best!

[david....@gmail.com]

Yes, thank you for your great service!

[sqliph...@gmail.com]

Yes It was answered in Chat.

Thank you very much.

[david....@gmail.com]

I am still unable to download files with spaces in the name.  Ricardo said there was a fix coming soon. Any update?

[winapp....@gmail.com]

Hi Davi,

I migrated just now.  But still I can able to see the parse url. http://files.parsetfss.com/cfdd6e16-8ac4-4830-bd73-fcfd445be6d1/tfss-1468c13a-35cf-410c-9674-0287b7e6565a-12592426_1127983007241957_6881689740717646031_n.jpg 

And the file is not loading. Could you please help me to assist?

[Antônio Castro]

Hi.

Unfortunately the files are not available anymore in parse.com and it is not possible to migrate.

Best.

--
You received this message because you are subscribed to the Google Groups "back{4}app" group.
To unsubscribe from this group and stop receiving emails from it, send an email to back4app+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/back4app/a80cfd72-83ae-4b8c-8564-b6112ee2dd1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.