ReportAway!®

We have had at least one report of a user running BlackBerry OS 5.0 Beta that was unable to send reports from ReportAway! . Following downgrade to a supported OS for their device, the issue was resolved.

Unfortunately, we cannot support ReportAway! on beta versions of OS. When OS 5.0 becomes a generally available OS, we will make sure ReportAway! operates correctly on it.

If you are successfully using ReportAway! on a beta version of OS 5.0 please reply to this thread with an indication of your device model and details of the OS and platform build. This information is typically the first 3 lines of the BlackBerry's "Options->About" screen.

I just installed the latest ReportAway! 1.3.0.1 on my BB tour. I am running a beta version of OS 5.0.0.230 and the ReportAway! seems to run fine.

Options->About is:
Blackberry 9630
smartphone (3G,CDMA)
v5.0.0.230 (platform 4.2.0.61)

I can send reports just fine at the moment.

OK. I stand corrected. Technically this does NOT work on OS 5.0.230. But, since I use BIS I have all emails sent from my berry BCC'ed to another address so I can keep track of sent emails. What is happening is that I receive the BCC version of the email since it is controlled by the BIS service at RIM. However, I do NOT receive the email specified in the TO line. I looked at the raw headers and it appears that the TO email address is being stripped off when it is sent from the berry. Therefore it dies somewhere along the line and you never know.

So, I kinda backed into a temporary solution by just using the BCC'ed version so I can import into QB. It works fine. I understand that the folks at Acire can not really support the application on a Beta OS. But, I just wanted to mention what works and does not work for me to help in the development of the software.

Thanks
MIke

mtills wrote:
OK. I stand corrected. Technically this does NOT work on OS 5.0.230. But, since I use BIS I have all emails sent from my berry BCC'ed to another address so I can keep track of sent emails. What is happening is that I receive the BCC version of the email since it is controlled by the BIS service at RIM. However, I do NOT receive the email specified in the TO line. I looked at the raw headers and it appears that the TO email address is being stripped off when it is sent from the berry. Therefore it dies somewhere along the line and you never know.

So, I kinda backed into a temporary solution by just using the BCC'ed version so I can import into QB. It works fine. I understand that the folks at Acire can not really support the application on a Beta OS. But, I just wanted to mention what works and does not work for me to help in the development of the software.

Thanks
MIke

Thanks for the input Mike, it helps us characterize this problem. It is very interesting that things work through BIS for the address on the BCC line. The user that reported the original problem was on a BIS service and running V5.0.0.190. They could not get this to work on their BIS service. So it is a bit of a mystery why this works for the address in the BCC line.

Thanks...Actually, I think it works via BCC because the email leaves my blackberry and hits the BIS servers before it goes anywhere. Since I have the "auto BCC" set in the blackberry portal the BIS stuffs the BCC in there. That is why I get it on my autobcc account. Perhaps this other person was not using autoBCC through BIS. It is disabled by default. So it appears that reportaway is losing the TO portion of the email somewhere under the latest beta versions of OS 5.0. It is interesting that the email dialog box right after I select "Report All" option shows the FROM and the TO so it appears it is being stripped/lost as soon as I select SEND from that diaglog box.

The autobcc thing was more of a workaround and works well for me.

Thanks

We did extensive testing of OS5.0 when we released 1.4.0. So while I am convinced there was an issue when running on older beta releases of OS5.0 I am confident this issue has been resolved.