Issue after migrating to Parse Server #317

Activity

1. drew-gross commented on Feb 9, 2016

   

   drew-gross

   on Feb 9, 2016

   Contributor

   More actions

   Can you run the server with VERBOSE=1 and tell us what the output is when you make the failing query? If there is no output, then this is probably an issue with the Android SDK, in which case you should open an issue with the Android SDK repo.
2. kumarkeviv commented on Feb 9, 2016

   

   kumarkeviv

   on Feb 9, 2016

   Author

   More actions

   I don't know how to turn the verbose=1 in azure for webapp, could you guide the steps because i can only see verbose in azure for their cloud services.
3. drew-gross commented on Feb 10, 2016

   

   drew-gross

   on Feb 10, 2016

   Contributor

   More actions

   VERBOSE is an environment variable, you set it the same way as any other environment variable.
4. christianmarth commented on Feb 10, 2016

   

   christianmarth

   on Feb 10, 2016

   More actions

   Have you also updated the bolts framework? It appears the no class def
   error relates to Bolts

   On Wednesday, 10 February 2016, Drew <notifications@github.com
   javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

   VERBOSE is an environment variable, you set it the same way as any other
   environment variable.

   —
   Reply to this email directly or view it on GitHub
   #317 (comment)
   .

   Kind Regards

   Christian Marth | Director

   App Fibre (Singapore) Pte. Ltd.
   8 Jurong Town Hall Road
   The JTC Summit #24-05
   Singapore 609434
   *Phone: *+65 8142 5242
   *UEN: *201419241N
   *Facebook: *facebook.com/appfibre https://www.facebook.com/appfibre

   *Skype: *christian.marth
   *LinkedIn: *au.linkedin.com/in/christianmarth

   Our company accepts no liability for the content of this email, or for the
   consequences of any actions taken on the basis of the information provided,
   unless that information is subsequently confirmed in writing. If you are
   not the intended recipient you are notified that disclosing, copying,
   distributing or taking any action in reliance on the contents of this
   information is strictly prohibited.
5. kumarkeviv commented on Feb 10, 2016

   

   kumarkeviv

   on Feb 10, 2016

   Author

   More actions

   Hi Drew and Christian

   The previous issue is resolved it was the SDK's issue as Drew suggested.

   Now when I am hitting the parse server hosted on Azure, I am not getting any response its just throwing an exception that JSON response is not in correct format.

   I have hosted my parse server here: http://hr-interview.azurewebsites.net/

   Also my definition for Initialization in Application file of app is here:

   Parse.initialize(new Parse.Configuration.Builder(getBaseContext())
   .applicationId("xxxxxxxxxxxxxxxxxxxx")
   .clientKey("xxxxxxxxxxxxxxxxxxxxx")
   .server("http://hr-interview.azurewebsites.net")
   .build()
   );

   I am using the same appid and client id i was using in parse. Am I missing something?
6. drew-gross commented on Feb 10, 2016

   

   drew-gross

   on Feb 10, 2016

   Contributor

   More actions

   Incorrect JSON format sounds more like a parse-server issue. Can you use the VEBOSE environment variable like I mentioned above and paste the output of the server here?
7. kumarkeviv commented on Feb 10, 2016

   

   kumarkeviv

   on Feb 10, 2016

   Author

   More actions

   Hi Drew

   I have enabled the verbose=1, also i have downloaded the diagnostics files. But I can't find much in the log. I can see that the request is hitting cloud as the REQUEST is visible on dashboard.

   Please find the trace I got at this link:
   https://www.dropbox.com/sh/f0e7oxqkckancow/AACz5QNbtd212exx6yw8ob_ia?dl=0

   Let me know, if i need to do anything more.
8. drew-gross commented on Feb 10, 2016

   

   drew-gross

   on Feb 10, 2016

   Contributor

   More actions

   There are a lot of files in that folder. With VERBOSE enabled, you should see an request body and response in your server's output. Can you paste the output for a single failing request here?
9. drew-gross

   added

   troubleshooting

   on Feb 11, 2016
10. kumarkeviv commented on Feb 11, 2016

    

    kumarkeviv

    on Feb 11, 2016

    Author

    More actions

    Hi Drew

    The issue has been resolved, and you can close this now. Thanks for your help.
11. otymartin commented on Feb 11, 2016

    

    otymartin

    on Feb 11, 2016

    More actions

    @kumarkeviv What was your solution?
12. drew-gross

    closed this as completedon Feb 11, 2016
13. mjoshinath commented on Mar 11, 2016

    

    mjoshinath

    on Mar 11, 2016

    More actions

    Hi Drew, i have the same issue as mentioned above and i have tried setting VERBOSE value to 1 and even then no change, here is an error

    FATAL EXCEPTION: main
    java.lang.NoClassDefFoundError: bolts.TaskCompletionSource
    at com.parse.ParseQuery$5$1.then(ParseQuery.java:1289)
    at com.parse.ParseQuery$5$1.then(ParseQuery.java:1285)
    at bolts.Task$14.run(Task.java:796)
    at bolts.BoltsExecutors$ImmediateExecutor.execute(BoltsExecutors.java:105)
    at bolts.Task.completeAfterTask(Task.java:787)
    at bolts.Task.continueWithTask(Task.java:599)
    at bolts.Task.continueWithTask(Task.java:610)
    at bolts.Task$12.then(Task.java:702)
    at bolts.Task$12.then(Task.java:690)
    at bolts.Task$14.run(Task.java:796)
    at bolts.BoltsExecutors$ImmediateExecutor.execute(BoltsExecutors.java:105)
    at bolts.Task.completeAfterTask(Task.java:787)
    at bolts.Task.continueWithTask(Task.java:599)
    at bolts.Task.continueWithTask(Task.java:574)
    at bolts.Task.onSuccessTask(Task.java:690)
    at bolts.Task.onSuccessTask(Task.java:680)
    at bolts.Task.onSuccessTask(Task.java:714)
    at com.parse.ParseQuery$5.call(ParseQuery.java:1285)
    at com.parse.ParseQuery$5.call(ParseQuery.java:1282)
    at com.parse.ParseQuery.doWithRunningCheck(ParseQuery.java:1154)
    at com.parse.ParseQuery.getFirstAsync(ParseQuery.java:1282)
    at com.parse.ParseQuery.getInBackground(ParseQuery.java:1503)
    at com.joshi.contactupdates.activities.SplashActivity.onCreate(SplashActivity.java:37)
    at android.app.Activity.performCreate(Activity.java:5104)
    at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1080)
    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2144)
    at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2230)
    at android.app.ActivityThread.access$600(ActivityThread.java:141)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1234)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loop(Looper.java:137)
    at android.app.ActivityThread.main(ActivityThread.java:5041)
    at java.lang.reflect.Method.invokeNative(Native Method)
    at java.lang.reflect.Method.invoke(Method.java:511)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
    at dalvik.system.NativeStart.main(Native Method)
14. drew-gross commented on Mar 11, 2016

    

    drew-gross

    on Mar 11, 2016

    Contributor

    More actions

    We determined that this issue is an Android SDK issue, can you check the Android SDK repo for help?
15. mjoshinath commented on Mar 11, 2016

    

    mjoshinath

    on Mar 11, 2016

    More actions

    Hey drew, problem solved but with upgradation of facebook sdk dependency to 4.9.0, Thanks
16. mtrezza

    added

    type:questionSupport or code-level questionSupport or code-level question

    and removed

    🔧 troubleshooting

    on Jul 11, 2021