---
title: Resolved Known Issues
slug: help/en-us/pocketcowcard/resolved-known-issues
docTags: 
createdAt: 2026-09-17T17:47:06.152Z
---

<font color="#99BA4D">~~**RESOLVED**~~ </font>**&#x20;2026/03/03 - Remove the refresh error message:&#x20;**&#x50;ocket CowCard may display a "No syncable transactions were found" error message when you try to refresh. This error may occur if you click on a list without picking an animal or activate a list and focus on PEN=0, then exit. This will be fixed in a future release.

To remove the message and refresh Pocket CowCard, follow the steps below:

1. Click **OK** to exit the message.
2. Tap **Review Transactions** on the Home screen.

::Image[]{src="https://dc-help.vas.com/Resources/Images/whats-new/26.3-refresh-1.png" size="20" width="695" height="685" isUploading="false" darkWidth="695" darkHeight="685" position="flex-start" showCaption="false" indent="1"}

3. Follow the guidelines when selecting transactions to erase:

   - Check the box next to transactions that aren't related to ID entry or event entry.
   - Do not check any boxes next to queued animal transactions. Check why they are not marked as **Done** in the hospital or vet list.


   ::Image[]{src="https://dc-help.vas.com/Resources/Images/whats-new/26.3-refresh-2.png" size="20" width="788" height="685" isUploading="false" darkWidth="788" darkHeight="685" position="flex-start" showCaption="false"}
4. Tap **Erase Transactions**, then tap **Yes** to confirm your choice.

:::Paragraph{indent="1"}
Pocket CowCard should now refresh correctly.
:::

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2025/09/18 - View full animal IDs in grid view workaround:&#x20;**&#x49;f your animal IDs are getting cut off when you view them in grid view, change the font size on your Pocket CowCard device so you can view the full ID. Follow the steps below to update your device's font size:

:::hint{type="success"}
🗒️ **NOTE:** Android settings may vary depending on the device. Contact Us if you need more help.
:::

1. Open **Settings** on your device.
2. Go to **Display**.
3. Tap **Font size and style**, then select the smallest option.
4. Return to the **Display** screen.
5. Tap **Screen zoom** or **Display size**, then select the smallest option.
6. Close and reopen Pocket CowCard. When you switch to grid view, the full animal ID will now be visible.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2025/06/18 - Send all records to DC305 before initiating Batch commands:&#x20;**&#x57;e have successfully identified the root causes for Cow Not Found error messages and subsequent transaction failures. The issue arises when new animals are added through the CowCard tab or worklists. Subsequently, Expert or Simple Batch commands are utilized prior to a full data transmission. This sequence prevents the submission of further transactions. A solution is currently being prioritized for immediate implementation. As a temporary workaround, users should send all newly added records to DC305 before initiating any Batch workflows.

<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2025/05/01 - Fix inaccurate TODO counts after a rare workflow:** The TODO counts may be inaccurate if you activate a vet list using the following steps: open the Cows tab, click on an animal, navigate past Pen Validation, exit the CowCard, click the LISTS tab, and activate a vet list. If the TODO counts do not match, close and reopen the vet list to fix the TODO counts.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2025/03/24 - Enter Breeding Codes on BRED events from the CowCard tab:&#x20;**&#x49;f you enabled the setting to force Breeding Codes when you enter a BRED event from the CowCard tab, make sure you enter a Breeding Code when you enter the BRED event. If you do not enter a Breeding Code before accepting your BRED event updates, the app may crash. This does not affect Breeding Grid entries.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2025/03/07 - Rare workflow results in lost data between Pocket CowCard and DairyComp if you switch herds:&#x20;**&#x57;e found a situation where Pocket CowCard does not send data correctly to DairyComp if you switch herds without sending the herd's data to DairyComp first. If you refresh multiple herds on a Pocket CowCard device, send each herd's data to DairyComp before you switch herds. We are looking into how to resolve this rare issue.

<font color="#99BA4D">~~**EXPIRED**~~</font>**&#x20;2025/01/27 - PCC may not show the correct DONE count on the LISTS screen:&#xA0;**&#x49;n testing, VAS identified a bug where the LISTS view did not show the correct DONE count. If you experience this issue, check (long press) and uncheck (long press) the worklist to correct the totals: 

VAS has not been able to recreate this issue, and we ask that you contact [VAS Support](http://dc-help.vas.com/default.htm#cshid=2000) if you encounter this bug.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2025/01/21 - Pocket CowCard does not warn you if you enter an undefined pen:&#x20;**&#x57;e found an issue where Pocket CowCard does not show a warning if you enter a pen that is not defined in DC305 during a MOVE event. Ensure that you do not have any undefined pens by running a summary by pen report in DC305. This will be fixed in the next Pocket CowCard release.

<font color="#99BA4D">~~**EXPIRED**~~</font>**&#x20;2024/10/29 - PCC needs more details from devices that fail to make transactions:** We have a special debug version to collect more information for certain “edge cases” where transactions are either not getting created or partially getting created. Please reach out to your support specialist if you have a device that is experiencing this issue: [VAS Support](http://dc-help.vas.com/default.htm#cshid=2000). "Edge cases" are situations where we cannot replicate the issue for various reasons. These cases might be device-related, OS-related, Cowfile-related, or related to a certain cadence used in the workflow. Videos of cadence workflow are helpful.

~~****~~<font color="#99BA4D">~~**EXPIRED**~~</font>**&#x20;2023/09/20 – Pen validation error in the new Item Entry feature:&#x20;**&#x57;e found an issue that occurs if you use pen validation during new item entry on a CowCard on an Android device that uses OS version 8.1 or 9.0. If the system asks you about pen validation and you select the **Don't ask me again** option, the system will automatically send the new item to DairyComp 305. If you must perform pen validations during item entry, use the SIMPLE BATCH command to avoid this error.

::Image[]{src="https://dc-help.vas.com/Resources/Images/whats-new/pcc-pki-cowexistsmessage-july23.png" size="20" width="512" height="282" isUploading="false" darkWidth="512" darkHeight="282" position="flex-start" showCaption="false" indent="1"}

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2023/07/19 – Older versions of Pocket CowCard may crash when adding an existing animal to a herd:&#x20;**&#x50;reviously, we noted that Pocket CowCard would crash if you used the ADD BATCH command to add an existing animal to a herd if the herd used source farm identifier items (SF and SFID). This issue only affected older Pocket CowCard versions.

Upgrade to the latest version of Pocket CowCard to get the fix: [Manually Update the App on your Android Device](docId\:gaEy8eBL5fxc11UoZN-Rg). In the latest version of Pocket CowCard, the system notifies you that the existing animal already exists and does not process the command.

::Image[]{src="https://dc-help-review.vas.com/Resources/Images/whats-new/pcc-pki-cowexistsmessage-july23.png" size="20" width="512" height="282" isUploading="false" darkWidth="512" darkHeight="282" position="flex-start" showCaption="false" indent="1"}

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2023/06/19 - Pocket CowCard may crash when entering a BRED event using the Enhanced VET FORM:&#x20;**&#x50;ocket CowCard may crash if you try to enter a BRED event by selecting **Other Event**, and then **BRED**. This only occurs if you have enabled [Enhanced Vet Form](docId\:vmEsPfLlIrsIWN1H3phyv) by selecting the **Use faster workflow for Vet Entry** setting.

::Image[]{src="https://dc-help-review.vas.com/Resources/Images/whats-new/usefastwfvetentry.png" size="10" width="236" height="381" isUploading="false" darkWidth="236" darkHeight="381" position="flex-start" showCaption="false" indent="1"}

:::ExpandableHeading
**Click here to view our recommended workaround.**

When Enhanced VET FORM is enabled, use the steps below to add a BRED event.

::Image[]{src="https://dc-help-review.vas.com/Resources/Images/whats-new/pcc-workaround-0620.png" size="30" width="1533" height="658" isUploading="false" darkWidth="1533" darkHeight="658" position="flex-start" showCaption="false"}

- Tap **View** from the Vet Entry form to open the CowCard.
- Tap **New Event** to open a list of events.
- Select the **BRED** event.
- Enter the BRED event details and tap **Accept**:
:::

~~****~~<font color="#882255">~~**KNOWN ISSUE**~~</font>**&#x20;2023/04/10 - Pocket CowCard unable to recognize 2 separate animals when using a Source Farm ID with ADDBATCH commands:&#x20;**&#x57;hen using this feature in DC305 to add two or more animals with the same visual ID (SFID) in the same session, the application is unable to recognize that there are 2 separate animals. We are working to add the necessary logic to this workflow in a future release. As a workaround, please type the complete identification (SF+SFID and any preceding zeros) in cases where 2 or more animals are added in the same collection session.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2022/10/12 – Some Batch menu entries are not being collected:&#x20;**&#x54;here have been a few cases where the system loses new entries created from the Batch menu on Pocket CowCardAndroid. The loss only occurs if you edit the Expert Batch command after you have already started entering data for a batch or if you do not refresh the device before you start entering data for a new batch. We are working diligently to resolve this issue. We have had no reports that ADD batch is affected. If you experience this issue, contact VAS Support before you refresh the device. There may be a chance that we can recover missing data before you refresh.

::::ExpandableHeading
**Click here to view our recommended workarounds.**

- Consider upgrading Pocket CowCard to the latest version and rebooting your device daily.
- Send collected batch data to DairyComp before you enter a new batch.
- Only edit the expert batch command after you have sent collected data and before you enter a new batch using the new expert batch command.
- Refresh the device before you enter a new batch.
- Alternatively, you can create specific Pocket CowCard commands for each new batch entry. For example, if you want to create a SHIP event and collect data for multiple lots in separate transactions, you can create specific commands for each lot:
  1. To collect data for the first lot, enter the following command in the command line. In this example, we collect data for lot 16:

:::Paragraph{indent="3"}
**Create ZSHP16:**
:::

:::Paragraph{indent="3"}
ENTER\Z EC=32 EDAY=SCDAT PEN=999 **LOT=16**
:::

:::Paragraph{listStyleType="decimal" listStart="2" indent="2"}
To collect data for a new lot, re-enter the command in the command line and replace the existing lot number with the new lot number:
:::

:::Paragraph{indent="3"}
**Create ZSHP62:**
:::

:::Paragraph{indent="3"}
ENTER\Z EC=32 EDAY=SCDAT PEN=999 **LOT=62**
:::

:::Paragraph{listStyleType="decimal" listStart="3" indent="2"}
Repeat this command and replace the lot number for each lot you need to enter.
:::
::::

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2022/12/15 - When adding a new record by scanning from the CowCard or worklists, the record is sent to DairyComp as an ADD and is not being held on the DairyComp server:&#x20;**&#x57;ith this bug, new records are being sent to DC305 when scanning in CowCards and worklists. We are working on a fix that will hold the records back on the DairyComp server. Additionally, the fix will do the same with Expert Batch.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2022/10/21 - After refreshing a new herd, an error message warns that the new herd has unposted data:&#x20;**&#x54;he system displays an error message after you refresh a new herd to your existing Pocket CowCard app. Until we can resolve the issue in a future update, follow these steps if the system display the Unposted data error message.

::Image[]{src="https://dc-help.vas.com/Resources/Images/whats-new/pcc-oct22-unposterror.png" size="30" width="1445" height="707" isUploading="false" darkWidth="1445" darkHeight="707" position="flex-start" showCaption="false" indent="1"}

1. Tap **Open \[HERDCODE]**. Instead of **\[HERDCODE]**, the system displays your actual herdcode.
2. Tap **Continue**.
3. Tap **Abort Changes**.
4. Enter the new herd's herdcode, then tap **Accept**.

After completing the steps, the system should no longer display the error message if you refresh the new herd again unless the app is deleted. If the workaround fails and the system displays the message again, contact VAS Support.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2022/10/04 - Unsupported events shown in SERVER\3 settings:&#x20;**&#x57;hen we started supporting events higher than 63 for cowfile 9 users, we discovered a bug for all users. You may now see the option to select FRESH, CALFVAC, and COMBO events on Pocket CowCard, but Pocket CowCard does not support these events. Do not use these events on Pocket CowCard. This issue will be resolved in a future release.

::Image[]{src="https://dc-help-review.vas.com/Resources/Images/whats-new/pcc-supportedevents.png" size="20" width="1083" height="641" isUploading="false" darkWidth="1083" darkHeight="641" position="flex-start" showCaption="false" indent="1"}

All other events are now supported. If you do not want to use certain events that are now supported, inform your staff that they should not use them.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2022/09/26 - Backups for ADD BATCH routines do not include EIDs:&#x20;**&#x57;hen you use an ADD BATCH routine with a scanner, the system will send a backup without EIDs for the new records if you allow transaction backups. Until we can resolve this issue, if you plan to use any ADD BATCH routines with a scanner, we recommend deselecting the **Allow backups of transactions** option in the **Settings** tab. If you do are not using an ADD BATCH routine with a scanner, check the box to enable transaction backups.

::Image[]{src="https://dc-help-review.vas.com/Resources/Images/whats-new/pcc-addbatch.png" size="20" width="768" height="742" isUploading="false" darkWidth="768" darkHeight="742" position="flex-start" showCaption="false" indent="1"}

~~****~~<font color="#99BA4D">~~**EXPIRED**~~</font>**&#x20;2022/02/22 – Support for Android 6 OS and earlier ends on 8/15/2022:&#x20;**&#x50;ocket CowCard support for older Android OS versions has ended, so please upgrade or replace your device.

~~****~~<font color="#99BA4D">~~**EXPIRED**~~</font>**&#x20;2021/12/31 – Version 5 cowfiles are not supported in Pocket CowCard Android:&#x20;**&#x53;upport for Version 5 cowfiles on Pocket CowCard Android ended in 2019. Any changes made after support ended are not compatible with older version cowfiles like 3, 5, and 7.

~~****~~<font color="#99BA4D">~~**EXPIRED**~~</font>**&#x20;2021/10/29 – Android 11 runs very slowly with the app installed on the SC card:&#x20;**&#x54;here is a known issue that affects Pocket CowCard Android when using devices with Android 11 with an SD card and large worklists. Our current recommendation is to only use devices in the 8.1 to 10.0 versions of Android while working with large worklists. We are working on alternatives for handling the changes Google is making with apps that are installed on the SD card. Please refer to the chart below for which devices to use for Pocket CowCard Android. You can learn more about this on the Reddit forum.

::Image[]{src="https://dc-help-review.vas.com/Resources/Images/whats-new/pcc-version-chart.png" size="20" width="969" height="403" isUploading="false" darkWidth="969" darkHeight="403" position="flex-start" showCaption="false" indent="1"}

~~****~~<font color="#99BA4D">~~**EXPIRED**~~</font>**&#x20;2021/06/08 – List completion percentages on some devices:&#x20;**&#x54;here is a known bug that affects certain OS versions of devices on the list's completion percentage. Re-installing the app solves this issue in the intermediary. This issue will be watched to see if a pattern develops, as it is presently difficult to reproduce across all devices.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2021/06/08 – PIN codes for Pocket CowCard Android are here; your device ID may change:&#x20;**&#x50;lease consider using the PIN codes in DairyComp for controlling the devices that refresh from your DairyComp Server. Specifications from Google require that we move to using Android ID, which may cause your device ID to no longer be available. PRO SCAN and Pocket Breeder Android users will retain their license but need a PIN code to access a herd that has PIN codes activated. Windows Mobile users are not affected by this change. See this video for more details.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2021/05/12 – IMPORTANT: Users must allow all permissions to use the Pocket CowCard app:&#x20;**&#x50;lease allow all permissions on any releases dated after 2021/03/31. The app will guide you through the permission process upon installation.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2020/12/23 – IMPORTANT: RFID scanning with outstanding prompts may cause crashes:&#x20;**&#x56;AS recommends responding to any screen prompts before proceeding to the next RFID scan. Continuing to scan animals with outstanding prompts causes known issues in the Vet Form, Hospital Form, and Breeding Grid. We are investigating these issues and will address them in a future release.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2021/04/22 – IMPORTANT: Users must allow all permissions to use the Pocket CowCard app; Device ID may change:&#x20;**&#x57;hen installing the Pocket CowCard app, users MUST allow all permissions. The app will guide you through the permission process during installation. Also, many users will be informed that their device ID is no longer valid when using higher versions of Android devices. Users configured for Pocket CowCard Unlimited (i.e., those using goodwill certificates) should not be impacted. Please contact VAS Support to update your Pocket CowCard certificates if you are not using goodwill certificates or are a Pocket CowCard Pro user.

~~****~~<font color="#99BA4D">~~**EXPIRED**~~</font>**&#x20;2020/12/03 – Must use the COW tab when using multiple TODO lists:&#x20;**&#x57;e have encountered issues when processing multiple worklists from outside of the COW tab, as the app only finds animals on the list that you currently have open. VAS recommends only working from the COW tab when processing multiple lists. Or, an even better solution is to redo your worklists into a single list. The option to process multiple lists concurrently is becoming increasingly complicated and is not sustainable on the Mobile Platform in the long run. This feature will be deprecated in favor of speed, dependability, and simplicity.

~~****~~<font color="#99BA4D">~~**WORKAROUND**~~</font>**&#x20;2020/11/17 – How to prevent an Android Device from auto-updating its OS:&#x20;**&#x54;o prevent issues in the future, please turn off your device’s ability to auto update its OS, see basic example for 9.0 devices:

1. Swipe down from the top edge of your screen to reveal the quick settings menu.
2. Tap the cog (also called ‘gear’) icon, which is usually in the upper right corner.
3. Tap “Software Update” from the list of options.
4. Deselect “Download updates automatically”.
5. Make sure all options are deselected.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2020/08/04 – Android 10/11 no longer supports the display of (IMEI) DEVICE IDs:&#x20;**&#x43;ustomers who are affected will need to contact support in the event their device is not registered and are not using “Good Will” Pocket CowCard license certificates.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2020/05/26 – DC305 license and application upgrade required:&#x20;**&#x46;uture improvements for the Android version of Pocket CowCard and the VAS Platform will require that you upgrade your Version 5 DC305 licenses to Version 8. An application upgrade to the XE version of DC305 will also be required.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2020/05/26 – Ending Pocket CowCard Android support for the DC305 Version 5 Cowfile/License:&#x20;**&#x54;o streamline programming and improve the support experience with Pocket CowCard Android, we are announcing an “End of Life” in supporting data exchange with the DC305 Version 5 Cowfile/License.****
**IMPORTANT:&#x20;**&#x43;ustomers are encouraged to migrate to the Version 8 Cowfile/License by December 31st, 2020 to continue using Pocket CowCard Android in 2021. Please contact your Sales/Support Specialist for assistance in making the needed upgrade to Version 8.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2020/05/19 – Update to Google's security regarding apps from unknown sources:&#x20;**&#x54;his is the first release where a new Google security notification has popped up for Pocket CowCard APK. Users must click **Install Anyway**, or else Pocket CowCard will not install.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2020/01/13 – CAUTION: Uninstalling the Pocket CowCard app will remove it and all associated data from your device:&#x20;**&#x54;his means you will lose all your custom settings, herd folders, unposted transactions, and archived transactions on the device if you uninstall the Pocket CowCard app. If you must uninstall your app, please deliver any unposted transactions to DC305 first, and then consider renaming your app folder COM.VAS.Pocket CowCard. We are looking at ways to preserve some of the content, if possible, based on how Google’s Android handles the uninstall process.

~~****~~<font color="#99BA4D">~~**EXPIRED**~~</font>**&#x20;2020/01/13 – The server that handles the distribution of the Pocket CowCard Android app will be discontinued soon:&#x20;**&#x57;e are planning to use the Google Play Store as the new method for distributing the Pocket CowCard Android app.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2019/12/12 – Scanning new animals into the herd from a TODO list or AD-HOC event:&#x20;**&#x53;canning of a new animal into the herd currently adds that animal to DC305 immediately. In a future Pocket CowCard Android release, we plan to match the current Windows Mobile functionality and instruct the DC305 Server to hold those new "add" transactions rather than immediately adding them to the system.

~~****~~<font color="#99BA4D">~~**RESOLVED**~~</font>**&#x20;2019/11/13 – Scan method overwrite:&#x20;**&#x53;can method items may be changed inadvertently from their original values when tapping on animals from the QUEUE or DONE tabs in worklists. For instance, an R or V method may update to a T. This issue will be addressed in an upcoming release.

~~****~~<font color="#99BA4D">~~**EXPIRED**~~</font>**&#x20;2019/10/11 – DC305 license and application upgrade required:&#x20;**&#x46;uture improvements for the Android version of Pocket CowCard and the VAS Platform will require that you upgrade your Version 5 DC305 licenses to Version 8. An application upgrade to the XE version of DC305 will also be required.

~~****~~<font color="#99BA4D">~~**EXPIRED**~~</font>**&#x20;2019/03/07 – Android Nougat 7.1.2, 8.1.0, and other newer versions cannot read 8-digit SD Card – Pocket CowCard-315:&#x20;**&#x47;oogle has removed the ability to read the 8-digit SD Card ID on newer versions of Android. The current method is to use the Device ID for the licensing of Pocket CowCard at the time of registration.
