Возникла ошибка illegalstateexception tivimate

Перейти к контенту

private void initScansForForm() {
        if (form == null) {
            return;
        }

        final String formId = form.getFormId();
        new Thread() {
            public void run() {
                List<Scan> scans = new ArrayList<>();
                Cursor c = db.fetchFormScans(formId);
                int id = 0;
                while (c.moveToNext()) {
                    if (!c.isNull(0)){
                        id = c.getInt(0);

                    }
                    else {
                        Log.d(TAG, "run: "+id);
                    }
                    int formId = c.getInt(1);
                    String scanTime = c.getString(2);
                    String locationName = c.getString(3);
                    double latitude = c.getDouble(4);
                    double longitude = c.getDouble(5);

                    scans.add(new Scan(id, formId, scanTime, locationName, latitude, longitude));
                }
                setScans(scans);
            }
        }.start();
    }
public Cursor fetchFormScans(@NonNull String formId) {
        return fetchFormScans(Integer.parseInt(formId));
    }


public Cursor fetchFormScans(@NonNull String formId) `enter code here`{
        return fetchFormScans(Integer.parseInt(formId));
 }

10-14 19:29:34.313  24409-24409/ru.endid.sqliteproject E/AndroidRuntime﹕ FATAL EXCEPTION: main 
    Process: ru.endid.sqliteproject, PID: 24409 
    java.lang.IllegalStateException: attempt to re-open an already-closed object: SQLiteQuery: SELECT _id, name FROM company ORDER BY name 
            at android.database.sqlite.SQLiteClosable.acquireReference(SQLiteClosable.java:55) 
            at android.database.sqlite.SQLiteQuery.fillWindow(SQLiteQuery.java:58) 
            at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:152) 
            at android.database.sqlite.SQLiteCursor.onMove(SQLiteCursor.java:124) 
            at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:214) 
            at android.database.CursorWrapper.moveToPosition(CursorWrapper.java:162) 
            at android.widget.CursorAdapter.getItemId(CursorAdapter.java:223) 
            at android.widget.AbsListView.onSaveInstanceState(AbsListView.java:1764) 
            at android.view.View.dispatchSaveInstanceState(View.java:12728) 
            at android.view.ViewGroup.dispatchFreezeSelfOnly(ViewGroup.java:2629) 
            at android.widget.AdapterView.dispatchSaveInstanceState(AdapterView.java:783) 
            at android.view.ViewGroup.dispatchSaveInstanceState(ViewGroup.java:2615) 
            at android.view.View.saveHierarchyState(View.java:12711) 
            at android.app.FragmentManagerImpl.saveFragmentViewState(FragmentManager.java:1577) 
            at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:951) 
            at android.app.FragmentManagerImpl.removeFragment(FragmentManager.java:1167) 
            at android.app.BackStackRecord.run(BackStackRecord.java:641) 
            at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1447) 
            at android.app.FragmentManagerImpl$1.run(FragmentManager.java:443) 
            at android.os.Handler.handleCallback(Handler.java:733) 
            at android.os.Handler.dispatchMessage(Handler.java:95) 
            at android.os.Looper.loop(Looper.java:136) 
            at android.app.ActivityThread.main(ActivityThread.java:5001) 
            at java.lang.reflect.Method.invokeNative(Native Method) 
            at java.lang.reflect.Method.invoke(Method.java:515) 
            at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785) 
            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601) 
            at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132) 
            at dalvik.system.NativeStart.main(Native Method)

Are you fond of using TiviMate to watch various shows and videos in your free time?

But maybe you have been seeing error codes every time you try to open TiviMate on your device.

It can be a frustrating and annoying experience but don’t feel disappointed because you can easily fix these errors.

In this article, we will be going over the various error codes that you might be facing in your TiviMate account and how you can fix them.

TiviMate Error Code 400

When you are seeing the error code 400 in TiviMate then that means there are some issues from your provider.

Error 400 in TiviMate can make you unable to load the page where you want to see the videos. 

This error code 400 can occur due to a bad gateway which can happen due to a poor internet connection or an issue on the service provider’s side. 

To fix the error code 400 you can check the internet connections to see if there are any loose connections or whether your internet is having any issues.

Another solution that you can try is to contact your service provider and talk to them about the issue.

The chances are that they will be able to fix it as in most cases error 400 happens due to an issue from their end.

TiviMate Error Code 401

When you are seeing the error code 401 on TiviMate you will not be able to load the list of channels in TiviMate.

Every time you try to load the list of channels you will see the message, “An error occurred: Code 401”.

This error occurs when your provider tries to block you from using other media players except their own in the device.

However, you can easily fix this error code 401 in your TiviMate.

To fix the error 401 you will have to open Settings and then General.

Now add “Agent: IPTVSmartersPlayer” to the User Agent.

Now try to open the list of channels again and you should be able to open it.

TiviMate Error Code 403

When you see the error code 403 on TiviMate then you will not be able to access your TiviMate channel. 

In most cases, this error 403 occurs when your provider has blocked you from accessing TiviMate.

It can also happen if TiviMate is blocked by another party in your region. 

To fix the issue of error 403 in TiviMate you can use a VPN to access your Tivimate account.

This can also be a temporary issue due to which you might be seeing the error code 403.

In that case, contacting your provider or waiting for some time can solve this issue.

TiviMate Error Code 404

If you see the error code 404 then that means the address can not be found that you have requested.

You will not be able to see the channel that you want and will only see the messages such as 404 Not Found, 404, 404 Error, Page Not Found, File Not Found, or Server Not Found. 

In most cases, this means that the address was changed somehow sometime ago and you are not aware of it.

Maybe this was changed by your provider. 

To fix this issue you can contact your provider and talk to them.

You can also check where the link that you have provided is correct.

You can also remove the channel from the list and then add them again and that should solve the issue. 

TiviMate Error Code 416

When you are seeing the error code 416 in your Tivi Mate then you will not be able to open TiviMate channels.

Error code 416 is a forbidden error code which means that the server has understood the request but has denied authorizing it.

A server’s inability to provide the requested ranges is indicated by the error code 416, Range Not Satisfiable.

The lack of such ranges in the document or the Range header value’s incomprehensibility as a whole is the most likely cause.

To fix this issue of error code 416 you will have to contact your service provider and then ask them to help you regarding this issue.

TiviMate Error Code 451

When you see the error code 451 then it means that your IPTV subscription is due and you will not be able to watch TV.

When you have not paid for the subscription even after your current subscription has expired you will see the error code 451.

To fix it you can just pay the subscription and your TV should be working as usual.

TiviMate Error Code 456

If you are seeing the error code 456 on TiviMate then you will not be able to open TiviMate and watch your videos. 

This error 456 is caused if your country lock is not reset by your provider. 

To fix this issue you can contact the provider and ask them to reset your country lock or you can just use a VPN with your system.

Using a VPN will also solve the issue but it is best that you get the country lock reset from your provider.

TiviMate Error Code 500

If you see the error code 500 you will not be able to open TiviMate and watch your favourite channels and shows. 

This error is caused by a server issue that can happen from your provider’s end.

To fix this issue please contact your service provider and ask them about it or you can wait for some time and see whether your error is solved during that time.

The chances are that the providers are updating the server so waiting should solve it most of the time.

TiviMate Error Code 502

When you are seeing the error code 502 then your TiviMate will be having issues connecting to its servers due to which you will not be able to open and watch videos in your TiviMate. 

The error 502 could be occurring due to server issues as well as due to having some kind of blockage in the connection.

To fix this issue you can try to force stop TiviMate and then open it again.

You can also clear the cache of TiviMate and then reboot the device.

If nothing works then please contact the service provider.

TiviMate Error Code 511

The error code 511 generally stops your TiviMate from getting network authorization and your videos will not get played when that happens. 

The cause of the error 511 in the TiviMate might be happening due to another app called Stalker on your device.

To fix this issue you can update your TiviMate to its latest version as this bug has been fixed in it.

You can also delete Stalker from your device to fix this issue. 

TiviMate Error Code 520

You could be seeing the error 520 when you are trying to open your IPTV.

This error will stop you from opening your TiviMate. 

The cause can be some kind of bug in the system of your device or maybe you forgot to update your TiviMate to its latest version.

To fix this issue you can uninstall and then reinstall it.

You can also sign out of your account and then sign in again and check whether the problem is happening.

Another solution is to check whether your TiviMate is updated to its latest version.

If it is not updated then you will have to update it and the error code 520 problem will get solved.

TiviMate Error Code 521

If you are seeing the error code 521 every time you are trying to open your TiviMate then you are probably unable to open it at all.

There can be various causes for error code 521 in your TiviMate.

Provider’s server could be down or refuse the connection because of some security reasons.

If you are using a VPN within your device then that can also be the reason why you might be seeing the error code 521.

To fix it first disable your VPN if you are using one.

If you can’t disable it then uninstalling it would solve the problem.

You can also contact your VPN provider and get TiviMate get whitelisted.

Another fix that you can try is to power cycle your router.

To do a power cycle you will have to unplug all the connections and then wait till all the lights have turned off and then replug them again and switch the router on.

If there is an issue with the server then there is nothing that you can do except wait till it gets fixed.

If nothing solves this issue then please contact your service provident and ask them about this issue.

Similar Posts:

Уважаемое хабрасообщество, вот вам загадка. Решаю уже несколько дней. Никогда до этого не связывался с мобильной разработкой, но черт дернул. Задумал приложение по работе с базой данных. А база большая, но это ничего. Все шло хорошо, пока я не добавил слишком много фрагментов и все не полетело в бездну.
Вводная:
В приложении есть несколько фрагментов с ListView. Они наполняются из базы при помощи связки SimpleCursorAdapter’a и Cursor Loader’а.
Предлагаю ознакомиться с логом ошибки:

10-14 19:29:34.313  24409-24409/ru.endid.sqliteproject E/AndroidRuntime﹕ FATAL EXCEPTION: main 
    Process: ru.endid.sqliteproject, PID: 24409 
    java.lang.IllegalStateException: attempt to re-open an already-closed object: SQLiteQuery: SELECT _id, name FROM company ORDER BY name 
            at android.database.sqlite.SQLiteClosable.acquireReference(SQLiteClosable.java:55) 
            at android.database.sqlite.SQLiteQuery.fillWindow(SQLiteQuery.java:58) 
            at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:152) 
            at android.database.sqlite.SQLiteCursor.onMove(SQLiteCursor.java:124) 
            at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:214) 
            at android.database.CursorWrapper.moveToPosition(CursorWrapper.java:162) 
            at android.widget.CursorAdapter.getItemId(CursorAdapter.java:223) 
            at android.widget.AbsListView.onSaveInstanceState(AbsListView.java:1764) 
            at android.view.View.dispatchSaveInstanceState(View.java:12728) 
            at android.view.ViewGroup.dispatchFreezeSelfOnly(ViewGroup.java:2629) 
            at android.widget.AdapterView.dispatchSaveInstanceState(AdapterView.java:783) 
            at android.view.ViewGroup.dispatchSaveInstanceState(ViewGroup.java:2615) 
            at android.view.View.saveHierarchyState(View.java:12711) 
            at android.app.FragmentManagerImpl.saveFragmentViewState(FragmentManager.java:1577) 
            at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:951) 
            at android.app.FragmentManagerImpl.removeFragment(FragmentManager.java:1167) 
            at android.app.BackStackRecord.run(BackStackRecord.java:641) 
            at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1447) 
            at android.app.FragmentManagerImpl$1.run(FragmentManager.java:443) 
            at android.os.Handler.handleCallback(Handler.java:733) 
            at android.os.Handler.dispatchMessage(Handler.java:95) 
            at android.os.Looper.loop(Looper.java:136) 
            at android.app.ActivityThread.main(ActivityThread.java:5001) 
            at java.lang.reflect.Method.invokeNative(Native Method) 
            at java.lang.reflect.Method.invoke(Method.java:515) 
            at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785) 
            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601) 
            at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132) 
            at dalvik.system.NativeStart.main(Native Method)

Как видно, нет отсылки к месту возникновения исключения в коде. Более того, попытки отловить его с помощью try — catch в местах, вызывающих подозрения, ничего не принесли. В первую очередь — это методы ContentProvider’а для доступа к базе. Вполне ожидаемо, что проблема с этим. Но нет! Так же были проверены методы Loader’a — чисто! В общем, кому интересно, предлагаю поискать вместе.
P.S. нашел точно такую же ошибку на багтрекере Mozilla здесь. Отличается только sql запросом. По крайней мере, я не одинок в своей проблеме.
P.P.S. Я не замещаю фрагменты, а использую метод add при добавлении нового. Потом, при возврате, забираю из BackStack предыдущий. Если заменить add на replace, ошибка исчезает. Значит, это напрямую связано с фрагментами и загрузчиком курсора. Но отловить ошибку не получается.