Showing Runtime Error Index 33, Size 0 Plz Help

Discuss
#35

You should really look again into your firebase token…

2019-02-05 10:14:26.718 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:29.347 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:29.574 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:29.763 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:29.763 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:31.351 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:31.351 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:31.575 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:31.575 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:33.589 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:33.589 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:33.876 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:33.876 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:35.160 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:35.160 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:35.406 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:35.407 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:35.619 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:35.619 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:36.008 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:40.681 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:45.205 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:45.706 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:45.906 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.
2019-02-05 10:14:49.579 27440-27440/? E/Firebase: Auth Failed: Could not parse auth token.

And this error happens if there is a problem with your firebase token.

1 Like
#36

Yes by removing admob ads from my app this error gone
But the problem is that why this error is causing using admob. My this application is also available on playstore i just want to update my app but now facing this problem

#37

Sir, now I have double checked my firebase token & URL both. Both are perfectly fine.
And one more user @Hadi_Editz confirmed that this runtime error is because of recent changes made in recent updates in admob ads component most probably admob banner component.

@Hadi_Editz, I suggest you to keep your app update on hold till kodular fix this issue in next update. Also I would like to know which admob ads you were using (Banner, Interstitial or Rewarded Video) ?

1 Like
#38

@Developer007 Banner and Interstitial brother

#39

I have Banner & Rewarded Video in my app.
@Mika sir problem is due to bug in banner ad component. I have confirmed the issue input. Now will kodular staff work on this in next update ?
Another issue that I came across while developing my app was - unable to make buttons invisible when a background image is set. For now I used solution given by you, put buttons in arrangement and making arrangement invisible. Thanx for that solution.

#40

bannertest.apk (5,0 MB)

Try this apk and tell me if you see a test ad after click on button 1

1 Like
Enforcing Admob Policies
Admob Ads not getting displayed (even test ads)
#43

Yes, An ad Appears both test and a real one… My old Comment seems to be Removed…

#44

You can not see a real ad…
IMPOSSIBLE!

Because the test apk above have test mode ON

#45

But I saw A real one… Like Boost Your traffic and things, It showed a Test Ad at first then it showed a Real one

Nope i did not take it

Okay will try

It Showed Once Though not anymore

#46

screenshot?

open the app again. see if real ads appear!

not appear? its not possible tho

#47

Same " Error index 1 size 0" with my app it just happened after exporting the apk today to share it with a friend to test it. I did not do any modification today just exported the apk. I tried to install the previous apk by asking my other friend if he still has the previous apk i sent him and its working.

update …
I’l try to remove the admob banner and see if the error will disappear .

3 Likes
#48

Same problum for me
Index 1 .

1 Like
#49

Until nobody makes a log for us using logcat we can not fix anything.

I can not reproduce all runtime errors above… since nobody provides a apk with detailed steps to get the error.

2 Likes
#50

Ad showing clicking after 30 seconds

#51

My two friends are also getting this error

1 Like
#52

i am also got this error

#53

Same Problem i am facing

#54

Lots of people are saying they have the same problem. While that is unfortunate, if you want help, please help provide some debug information.

Get an APK available for others with clear steps on how to recreate the issue. Use adb commands and get some details. Sure there are going to be bugs, however if we want to fix them, we need to understand them. To understand them we need to be able to replicate them.

Install adb on your devices and learn a few commands, to help get the details to isolate and solve.

3 Likes
#55

Can really nobody create a test apk with the error:
“Runtime Error Index 33, Size 0” or anything like this?
I dont want a test ad apk.
I want a apk with that exactly runtime error.
Else I can not know which thing the bug create.

1 Like
#56

I found this error happening when i used a cardview extension and it requires 4 fields of input as list and on a certain input i made a list and set it to a empty text box as a result the cardview Extension tried to get the 2nd items from that list and caused this error as well. I just mentioned it in case it helps