Download, print, export options don't work for assignment submission files

The Blackboard Instructor app doesn't support download or print functions for assignment files or annotations at this time. When users tap the Download icon, no action occurs. When users select Print from the menu, they can't successfully print the file or its annotations. Export options can be accessed, but don't work as expected.

Announcement push notifications for Ultra courses need to be enabled at system level

In most cases, push notifications for announcements are turned on at the system level. At this time, there isn’t a setting for users to turn announcement push notifications on or off in the app or web view of Blackboard Learn. If users aren’t receiving announcement push notifications for Ultra courses, please set the system default notification settings to "on" or "always on" in the admin panel. Note that they won’t be able to opt out of them at this time. More on default notification settings.

Force to web logins inflated in activity accumulator table

When the Mobile B2 is configured with Force to Web authentication, the activity accumulator table in the Blackboard Learn database records the Mobile Login Attempt multiple times for every mobile app user login on iOS and Android . This affects logins from both the Blackboard and Blackboard Instructor apps. This table shows how mobile usage activity statistics for logins will be inflated:

Blackboard App Requirements
Learn Version

Blackboard App

iOS

Blackboard Instructor App

iOS

Blackboard App

Android

Blackboard Instructor App

Android

Enterprise/Classic 2 entries 2 entries 3 entries 3 entries
SaaS 2 entries 2 entries 1 entry 1 entr

Blackboard Instructor not compatible with Session Fingerprint

Resolved in Blackboard Learn SaaS 3500.7+

The Blackboard Instructor app is not compatible with Session Fingerprint settings to create a new session when the fingerprint changes. Several types of content that are not supported in the native UI are loaded in an in-app browser (webView), which uses a different user agent than the native app view. The traffic for webView requests does not go through the mBaaS relay like native requests, so the remote IP address and user agent changes. Therefore, the user agent and IP address must change in any webView workflow, and attempting to create a new session upon a change to the session fingerprint causes a session failure in the webView in-app browser.


*Statements regarding our product development initiatives, including new products and future product upgrades, updates or enhancements represent our current intentions, but may be modified, delayed or abandoned without prior notice and there is no assurance that such offering, upgrades, updates or functionality will become available unless and until they have been made generally available to our customers.