Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>UPS Mobile is not linking to the Barcode Scanner app, but apparently have baked in its source code. This is not terribly shocking, even if it is unsupported and not recommended by the ZXing team.</p> <p>However, the UPS Mobile developers then did two things:</p> <ol> <li><p>They kept the same <code>&lt;intent-filter&gt;</code>, particularly where they are advertising that they are handling the <code>com.google.zxing.client.android.SCAN</code> action, despite the fact that they are not actually that app</p></li> <li><p>They marked the activity as not exported</p></li> </ol> <p>Courtesy of <a href="http://code.google.com/p/android/issues/detail?id=29535" rel="nofollow noreferrer">this bug</a>, the chooser will still show their activity, despite the fact that theirs is not exported and therefore cannot be launched.</p> <p>UPS Mobile either should be linking to Barcode Scanner the way you are, or not advertising this action. And, of course, this bug should get fixed.</p> <p>Unfortunately, the only workaround I can think of would be for you to add in your <code>Intent</code> the actual package name for Barcode Scanner (<code>com.google.zxing.client.android</code>) to try to limit it to that app only.</p> <p>This is reminiscent of <a href="https://stackoverflow.com/questions/10319928/android-securityexception-on-pdf-send-intent/10320136">another SO question</a>, that led to <a href="http://commonsware.com/blog/2012/04/25/how-isolated-adobe-reader-activity-issue.html" rel="nofollow noreferrer">a blog post of mine</a>, that obviously was insufficient to educate UPS, so I'll probably blog on this again...</p>
    singulars
    1. This table or related slice is empty.
    1. POUsing Zxing Barcode scanner causes SecurityException
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USCommonsWare
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUsing Zxing Barcode scanner causes SecurityException
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis is one of the big reasons we strongly discourage copy-and-paste of Barcode Scanner. It's typically the less-than-competent developers that need to copy, and they don't make necessary changes like the one you outline. Thanks for bringing it to light. If you use the supplied `IntentIntegrator` code in zxing (http://code.google.com/p/zxing/wiki/ScanningViaIntent), it will by default only select Barcode Scanner or Barcode Scanner+, using the mechanism you cite. Another reason to use our integration code rather than roll your own...
      singulars
      1. PO
      1. USSean Owen
    2. CO@SeanOwen: Ah, I hadn't looked inside `IntentIntegrator` recently -- glad to hear that you're tying it to your own project.
      singulars
      1. PO
      1. USCommonsWare
    3. CO@SeanOwen: I hadn't been using `IntentIntegrator`, but was just handling it myself. I appreciate the further education.
      singulars
      1. PO
      1. USkoopaking3
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload