美好的一天。我有可怕的情况。我在会话中创建一个位置共享逻辑。我将该会话保存在mysql上的服务器上。当android点击该活动时,我相应地插入用户信息。当android离开活动时我删除了那个列,所以会话被放弃了对方。在一个问题之前一切都很好.Android没有提供从最近刷掉应用程序的回调,meanging应用程序被彻底杀死。我在那里找到了一个工作。我正在使用一旦它达到我想要的活动就服务和启动服务。在服务中我有一个简单的事情叫做onTaskRemoved(),它通过从最近一次刷它来杀死应用程序时立即通知我。所有好到我要打电话的地方到我的服务器,以删除列。调用将不会通过,我将永远不会收到任何响应,但在onDestroy()一切正常工作。实际上这里是代码
@Override
public void onTaskRemoved(Intent rootIntent) {
destroySession();
super.onTaskRemoved(rootIntent);
}
private void destroySession() {
Log.d("Fsafasfsafasfas", "destroySession: " + opponentId + " my user id" + sharedHelper.getUserId());
Call<ResponseBody> locationCall = Retrofit.getInstance().getInkService().requestFriendLocation(sharedHelper.getUserId(), opponentId, "", "", Constants.LOCATION_REQUEST_TYPE_DELETE);
locationCall.enqueue(new Callback<ResponseBody>() {
@Override
public void onResponse(Call<ResponseBody> call, Response<ResponseBody> response) {
if (response == null) {
destroySession();
return;
}
if (response.body() == null) {
destroySession();
return;
}
try {
String responseBody = response.body().string();
Log.d("Fsafasfsafasfas", "onResponse: " + responseBody);
JSONObject jsonObject = new JSONObject(responseBody);
boolean success = jsonObject.optBoolean("success");
if (success) {
stopSelf();
} else {
destroySession();
}
} catch (IOException e) {
stopSelf();
e.printStackTrace();
} catch (JSONException e) {
stopSelf();
e.printStackTrace();
}
}
@Override
public void onFailure(Call<ResponseBody> call, Throwable t) {
destroySession();
}
});
}
电话永远不会通过,我猜是唯一打印的日志,是id的日志,仅此而已。任何人都有线索是怎么回事?我该如何处理这种情况?
答案 0 :(得分:3)
/**
* Created by Parag on 01/05/2017.
*/
public class AppService extends android.app.Service {
public static final String TAG=AppService.class.getName();
@Override
public int onStartCommand(Intent intent, int flags, int startId) {
Bundle bundle=intent.getExtras();
if(bundle!=null){
final String logout=bundle.getString("logout");
final String driverLoginId=bundle.getString("driverLoginId");
if(logout!=null&&driverLoginId!=null){
Toast.makeText(this, "logging out", Toast.LENGTH_SHORT).show();
Log.e(TAG,"Logging out");
Log.e(TAG,"Inside driverLogout "+driverLoginId);
Call<LogoutResponse> call = RestHandler.getApiService().driverLogout(driverLoginId);
call.enqueue(new Callback<LogoutResponse>() {
@Override
public void onResponse(Call<LogoutResponse> call, Response<LogoutResponse> response) {
//close the service on receiving response from API
Log.e("Response : ",response.body().getStatus()+"");
AppService.this.stopSelf();
}
@Override
public void onFailure(Call<LogoutResponse> call, Throwable t) {
//close the service on receiving response from API
AppService.this.stopSelf();
}
});
}else{
//Toast.makeText(this, "service starting", Toast.LENGTH_SHORT).show();
Log.e(TAG,"DriverLoginId : "+driverLoginId);
Log.e(TAG,"Logout : "+logout);
}
}else{
//Toast.makeText(this, "service starting", Toast.LENGTH_SHORT).show();
Log.e(TAG,"Service Start");
}
return super.onStartCommand(intent,flags,startId);
}
@Nullable
@Override
public IBinder onBind(Intent intent) {
return null;
}
@Override
public void onTaskRemoved(Intent rootIntent) {
Log.e(TAG,"Service Stop");
UserLocalStore userLocalStore=new UserLocalStore(AppService.this);
Log.e("USER DATA :",userLocalStore.fetchUserData().toString());
Intent restartServiceTask = new Intent(getApplicationContext(),this.getClass());
restartServiceTask.setPackage(getPackageName());
restartServiceTask.putExtra("logout","true");
restartServiceTask.putExtra("driverLoginId",userLocalStore.fetchUserData().getUserId());
PendingIntent restartPendingIntent =PendingIntent.getService(getApplicationContext(), 1,restartServiceTask, PendingIntent.FLAG_ONE_SHOT);
AlarmManager myAlarmService = (AlarmManager) getApplicationContext().getSystemService(Context.ALARM_SERVICE);
myAlarmService.set(
AlarmManager.ELAPSED_REALTIME,
SystemClock.elapsedRealtime() + 1000,
restartPendingIntent);
super.onTaskRemoved(rootIntent);
}
}
我也遇到了无法通过onTaskRemoved方法进行任何API调用的相同问题。 所以,我也研究了很多,但没有找到解决方案。所以,我终于想到了重新启动Web服务,并在intent中放置了一些额外内容。通过这种方式,您可以区分服务何时重新启动以执行API调用。
答案 1 :(得分:0)
我通过取消http请求的严格模式解决了这一问题。因此可以从主线程完成http请求。
StrictMode.ThreadPolicy policy = new StrictMode.ThreadPolicy.Builder().permitAll().build();
StrictMode.setThreadPolicy(policy);
在正常情况下建议这样做,但是当应用崩溃或关闭时,我认为可以发送一个http请求。