Hello,
I am trying to incorporate AdMod into an app.
I downloaded the AdMob library a few days ago.
I get the following error:
Compiling generated Java code. Error
B4A line: 31
Panel4.AddView(AdView1, 0dip, 0dip, 320dip, 50dip)
javac 1.6.0_21
src\canalrun\apps\aslalpha\main.java:202: cannot access com.google.ads.AdView
class file for com.google.ads.AdView not found
Searching the forums, I see somebody else has this problem and identified the solution. The forum post is shown below.
I would agree that this needs immediate attention. Maybe it's just a fix in the XML file - in which case he can do that ourselves.
Thanks,
Barry.
------------------------------------------------
Inman Inman is offline
Knows the basics
Join Date: Feb 2011
Posts: 63
Default
I think I found the issue. Looks like Admob made some changes to SDK JAR file, which was not updated in the B4A library. The obvious change is filename (from admob-sdk-android.rar to GoogleAdMobAdsSdk-4.0.2.jar). Then inside the JAR file, B4A expects the class file to be at com.admob.android.ads.AdView but the folder structure has changed to com.google.ads.Adview. The name of the Adview classes have also been changed in the Adview.class and may be other class files.
Most probably all this have to be due to Google's acquisition of Admob and they are changing all com.admob.android.ads references to com.google.ads. I hope Erel will update the B4A Admob library immediately. Till then Admob is unusable.
-------------------------------------------------
I am trying to incorporate AdMod into an app.
I downloaded the AdMob library a few days ago.
I get the following error:
Compiling generated Java code. Error
B4A line: 31
Panel4.AddView(AdView1, 0dip, 0dip, 320dip, 50dip)
javac 1.6.0_21
src\canalrun\apps\aslalpha\main.java:202: cannot access com.google.ads.AdView
class file for com.google.ads.AdView not found
Searching the forums, I see somebody else has this problem and identified the solution. The forum post is shown below.
I would agree that this needs immediate attention. Maybe it's just a fix in the XML file - in which case he can do that ourselves.
Thanks,
Barry.
------------------------------------------------
Inman Inman is offline
Knows the basics
Join Date: Feb 2011
Posts: 63
Default
I think I found the issue. Looks like Admob made some changes to SDK JAR file, which was not updated in the B4A library. The obvious change is filename (from admob-sdk-android.rar to GoogleAdMobAdsSdk-4.0.2.jar). Then inside the JAR file, B4A expects the class file to be at com.admob.android.ads.AdView but the folder structure has changed to com.google.ads.Adview. The name of the Adview classes have also been changed in the Adview.class and may be other class files.
Most probably all this have to be due to Google's acquisition of Admob and they are changing all com.admob.android.ads references to com.google.ads. I hope Erel will update the B4A Admob library immediately. Till then Admob is unusable.
-------------------------------------------------