Known Issues

LionPATH Mobile App not stable on Android 8 and 9 phones
(Posted August 17, 2018, 3:30 p.m. EST)

The LionPATH mobile app is not stable on Android 8 or 9 phones and use of the application is not currently supported. The vendor of the application is aware of the issue. If the issue is corrected, a newer version of the app will be published with Android 8 and 9 support. We apologize for the inconvenience.

Anyone having issues with the mobile app, please use the web version of LionPATH at lionpath.psu.edu.

Known Issue: Improper Use of Email Address Types
(Posted October 27, 2017)

Improperly using email address types and preferred email flags results in inaccurate information returned in queries, interfaces, and missed communications.

Resolution:
Proper use of “NONE GIVEN” email type: Staff should not assign the “NONE GIVEN” email type when it is populated with a valid email address. Queries and interfaces that call for the “OTHER” email type will receive incomplete data when the email address type is mis-marked.

Proper use of “UNIVERSITY” email type: Staff should not assign the “UNIVERSITY” email type. The “UNIVERSITY” email type is populated by central IT when the UNIVERSITY email is ready to be used (and removed when the “UNIVERSITY” email address is no longer available to the student). Adding a “UNIVERSITY” email to a record in LionPATH prior to it being assigned (or after it has been removed) results in missed communications.

The “PREFERRED” email flag should always be set to “UNIVERSITY” email type when there is a “UNIVERSITY” email type populated. When no “UNIVERSITY” email type is populated, the “PREFERRED” email flag should be set according to the following hierachy: “OTHER,” “FASFA STUDENT,” FAFSA PARENT.”

Known issue: SSNs updated in LionPATH are not sent to CIDR
(Posted October 6, 2017)

Updates to SSNs need be made directly in CIDR; these updates will then be updated in LionPATH.

The only scenario where SSNs are sent from LionPATH to CIDR is when adding a new record to LionPATH by adding bio data elements (not using a PSU ID).

Known issue: Undeclared and declared ethnicity data appearing in the same record
(Posted September 11, 2017)

There are converted prospect records that include ethnicity line items of “undeclared” along with other ethnicity choices. This scenario occurred due to adding ethnicity data to existing data when one or more applications were added for the prospect instead of replacing the previous data. This issue only relates to undergraduate records.

Resolution:
The “undeclared” ethnicity is being removed that chronologically appears before the other declared ethnicity data on these undergraduate records.

Known issue: Microsoft Excel converts some PSU IDs into a date format
(Posted April 2017)

Some PSU IDs convert into a date when they are imported into Excel (.csv format). For example, DEC5434 converts to Dec-34.

Resolution:
Interface files that are .csv format and contain the PSU ID should be opened in a text editor, and not in Microsoft Excel. This is to prevent some PSU IDs to be converted into dates by Excel.

Known issue: Passwords longer than 32 characters receive error in mobile app
(Posted June 2016)

Passwords longer then 32 characters will be truncated in the mobile app. Therefore, the LionPATH mobile app will not work for users with passwords longer then 32 characters. The password limit DOES NOT APPLY to the web version of LionPATH.

The actual text of the error messages the user will see:

“Error The server encountered an error 400 – Bad Request. Contact the administrator for help.” (Android)
“Error Authentication Error bad request” (iOS)

Resolution:
This is a known issue that we are working to resolve. For more information on the mobile app, visit the LionPATH app documentation: