You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to use Parse on windows with Android Studio.
I have followed tutorials on interned and created local parse server which is appering in parse dashboard, and passed this test http://localhost:1337/test , but when i run my project in android studio I get : com.parse.ParseRequest$ParseRequestException: i/o failure.
localhost means the device (or container) that is running the code. On iOS, if I run a simulator, local host works because my device is running on the computer, so it finds my server. But if I run a physical device, the phone has no local host.
You need a remote endpoint, which is where ngrok comes in.
I am trying to use Parse on windows with Android Studio.
I have followed tutorials on interned and created local parse server which is appering in parse dashboard, and passed this test http://localhost:1337/test , but when i run my project in android studio I get : com.parse.ParseRequest$ParseRequestException: i/o failure.
Here is my source code :
package com.example.mitaka.parsetest2;
import android.app.Application;
import android.util.Log;
import com.parse.Parse;
import com.parse.ParseACL;
import com.parse.ParseException;
import com.parse.ParseObject;
import com.parse.ParseUser;
import com.parse.SaveCallback;
public class StarterApplication extends Application {
@OverRide
public void onCreate() {
super.onCreate();
}
}
MainActivity:
public class MainActivity extends AppCompatActivity {
@OverRide
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
}
I have added:
allprojects {
repositories {
google()
jcenter()
maven { url 'https://jitpack.io' }
}
}
to buildGradle(Project)
and
implementation 'com.github.parse-community.Parse-SDK-Android:fcm:1.18.4'
to buildGradle(Module:app)
The text was updated successfully, but these errors were encountered: