03-28-2012 08:54 PM
I have no background in developing, I'm just introducing my self to it and doing so with webworks. I have a couple of issues and was wondering if somebody would kind enough to help me with them.
1. The most crucial one is with the debug token. When I try to package my app with the debug token I created I get an error: "The debug token pathname provided does not point to a file". Trust me I've checked and rechecked the path name and it's written down correctly, the debug token was successfully created. The path is also the correct one. I'm using a mac btw.
2. Can we use the advertising api with the playbook?
3. Can the ads api and bbm api be added to our apps using a mac? (the examples only show a windows based system)
4. How can I keep the footer at the bottom of the page regardless of the amount of content the page has?(without having it fixed)
Any help will be appreciated, thx in advanced.
Solved! Go to Solution.
03-30-2012 01:22 PM
1. Do you have the full path? Mine is Windows, but this is the line in my bbwp.properties file:
You may find the BlackBerry Graphical Tool of great use with Debug Tokens. I use it all the time:
2. The Ad SDK is not yet on PlayBook, though it's being worked on.
3. BBM is also not on PlayBook, but on the roadmap. These APIs should be usable on Mac for a Smartphone app though. They are really just Jars that need to be built into your application.
4. If you want to do work with headers and/or footers I would highly recommend using bbUI.js, as it's highly optimized for mobile and BlackBerry specifically.
03-30-2012 03:14 PM
Thank you so very much. I thought nobody was gonna reply to my call for help LOL. After taking a look at your post I went ahead and gave the ads sdk a try and it worked, again, thank you for that, haven't tried with the bbm sdk as of yet.
I already had the graphical tool installed but never occurred to my to try it out (d'oh). That been said, this tool also shows an error (sdk path is incorrect, I ran the configuration wizard), but I can live w/o this tool, I can just keep using the command line, but thank you for reminding me it's there and it's def easier than typing all of those commands into the command line, less room for errors.
In regards to the debug token I've tried everything to no avail, idk what else to do. I've tried the full path, using the "~" key and nothing.
So, can I sign a PB app and install it on my PB for testing? Or it has to be compile with a debug token for testing?
I'll definitely take a look at bbUI.js
03-30-2012 04:53 PM
You don't need to use a Debug Token. It just makes it easier to develop. If you sign the application you can test and install.
Can you post your line that describes your debug token location and I'll see if someone who's more of an expert with debug tokens and Mac's can suggest anything?
03-30-2012 06:16 PM
Tim you are very helpful
This is the path I'm using right now:
I've also used this one:
This wasn't the location where the debug token was created. I created this folder then cuted and pasted the token here. So maybe I shouldn't have moved the token?
04-04-2012 10:08 AM
I don't have a Mac, but the path needs to be a fully qualified path and I don't think it can support the ~ shortcut.
04-04-2012 01:11 PM
Tim once again to the rescue. This is the solution to my debug token issue. I can't thank you enough. Now the graphical aid app is working as it should and all thanks to you my friend. Now on to work with some issues I'm having with bbUI
04-25-2012 10:41 AM
04-25-2012 12:09 PM
If you're having issues compiling your app with the playbook's WebWorks SDK while having ads in your app, you probably pasted the blackberry.advertising folder in the playbook's bbwp/ext folder. Just erase the blackberry.advertising folder (in case you pasted it) from the playbook's bbwp/ext folder and try compiling your app again. Your ads will probably display but most likely you'll run into some issues while running your app. Hope this helps.
04-25-2012 12:35 PM
Yes, I removed all the advertising code and I'm back to where I was. I just wish in the WebWorks documentation, it would have said "only compatible with webworks for smartphones, NOT tablets".
Anyway... I really do hope they improve the webworks documentation in general.