ios - file_key parse server does not work -


i have been trying 6 weeks find out how fix problem parse server , legacy pffiles. not looking migrate legacy pffiles, use them in testing , development while parse maintains them. after testing, install s3 file adapter.

my app, running ios 9.3, written in objective c , stores images , video , runs fine while connected parse.com site. wanted test parse server , incrementally correct problems completed migration. however, have not been able correct (seemingly simple) failure occurs message {"code":1,"message":"internal server error."}.

my mongodb mlab , have appropriately included uri (and login) , filekey parse required. have information in app.config file, in environment of parse server instance on aws, , in appropriate references environment data via index.js file.

if query collection not have pffile items, query successful (i.e. normal). however, if query collection has pffiles query fails {"code":1,"message":"internal server error."}. cannot retrieve 1 record of such failed query in used selectkey in attempt bypass pffile objects.

the query is:

pfquery query = [pfquery querywithclassname:classname];       query.cachepolicy = kpfcachepolicynetworkonly;      [query wherekey:username equalto:[[pfuser currentuser]username]];      [query findobjectsinbackgroundwithblock:^(nsarray *objects, nserror *error)       {            if (!error)           {             ...            }           else nslog(@" %@", error);       }]; 

in testing able retrieve legacy files , test app such legacy data, supposedly available (according parse.com).

in index.js have included parse filekey:

var api = new parseserver({ databaseuri: databaseuri || 'mongodb://localhost:27017/dev', cloud: process.env.cloud_code_main || __dirname + '/cloud/main.js', appid: process.env.app_id || 'myappid', masterkey: process.env.master_key || '', //add master key here. keep secret! serverurl: process.env.server_url || 'http://localhost:1337/parse',  // don't forget change https if needed filekey: process.env.file_key || 'no file key', livequery: { classnames: ["posts", "comments"] // list of classes support query subscriptions    } });  

i have set environmental key file_key in nodes instance on ec2.

also, although redundant, have included file_key parameter in app.config file (of parse-server-example).

option_settings:   aws:elasticbeanstalk:application:environment:     parse_mount: "/parse"     app_id: "replacewithappid"     master_key: "replacewithmasterkey"     database_uri: "replacewithdatabaseuri"     node_env: "production"     server_url: "http://myappname.elasticbeanstalk.com/parse"     file_key: "parse filekey"   aws:elasticbeanstalk:container:nodejs:      nodecommand: "npm start" 

i have research previous posts , forums, , have taken @ parse ios sdk source code.

i realize filekey prefix pffile stored on s3 parse, , bucket name.

since no 1 seems have problem, must result of major oversight on part.

however, can help?

your problem might have solved now, file key variable in parse server initialisation seems in lower case incorrect. should filekey instead of filekey.


Comments

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

scala - 'wrong top statement declaration' when using slick in IntelliJ -