We've released an updated version of Pitcher Impact for iOS with new improvements and bug fixes

Login Prompts Fix

This release resolves an issue where some users were repeatedly prompted to log in to Salesforce after switching apps or returning from the background, even shortly after a successful login. Login sessions now stay active as expected, so you can move in and out of the app without unnecessary re-authentication prompts.

Polish Translation Corrections

We've corrected several Polish translations on the download options screen shown after login, making the wording clearer and more natural.

We've released an updated version of Pitcher Impact for iOS with new features and bug fixes

Smarter call subject naming Call subjects can now automatically show the contact's name together with the account name for one-on-one interactions, or just the account name when multiple contacts are involved, making it easier to identify calls at a glance in your calendar and planning views. This option is off by default and does not affect existing configurations unless enabled.

Fixes

• Status bar now visible during pre-call forms Resolved an issue where the status bar (time, battery, Wi-Fi) disappeared while filling out a pre-call form opened from Planning.
• Login and sync issue resolved Fixed a problem that could prevent some users from logging in and syncing after signing out of the app.
• Calendar display issue fixed Fixed an issue where a planned call scheduled by dragging and dropping onto the calendar could appear greyed out and become impossible to open.

We're happy to announce a new version of Pitcher Impact for Windows that includes new features and bug fixes

Passkey Login Support

Impact for Windows now supports signing in to Salesforce with a passkey. When your organization requires passkey-based multi-factor authentication, the Salesforce login step opens in your default browser instead of inside the app. Once verification completes, you are returned to Impact automatically. This applies to both the main app login (SSO) and the CRM connection login.

Why it matters

Salesforce has been rolling out mandatory passkey verification for certain user roles. The in-app login window cannot complete passkey verification, so users on those roles were unable to sign in. Handing the login step to the system browser, where passkeys are fully supported, lets those users complete verification and get back to work without workarounds.

Requirements

• A passkey already configured for your Salesforce user (e.g., via your organization's password manager).
• Latest version of Pitcher Impact for Windows (v2.142.2 or later)

Account Details Navigation Fix

Previously, opening the Account Details page from within Pitcher could unexpectedly prompt users to set up a passcode/MFA instead of taking them directly to the Salesforce Account record. This has been resolved, accessing Account Details now navigates correctly without an unnecessary authentication prompt.

Smarter call subject naming 

Call subjects can now automatically show the contact's name together with the account name for one-on-one interactions, or just the account name when multiple contacts are involved, making it easier to identify calls at a glance in your calendar and planning views. This option is off by default and does not affect existing configurations unless enabled.

We've released an updated version of Pitcher Impact for iOS with new features and improvements.

Improved login stability on iOS

We resolved an issue causing some users to be repeatedly prompted to log in throughout the day. This was traced to a session-handling issue that could invalidate a user's active session shortly after resuming the app. Logins are now more stable, with fewer unexpected interruptions.

Smoother single sign-on experience on iPad

We removed a false "You need to be online" warning that could briefly appear during single sign-on (SSO) logins on iPad, even when the login was completing successfully. This message was misleading and has now been suppressed so the sign-in flow feels cleaner and less alarming.

Passkey Login Support

What's new
Impact for iOS now supports signing in to Salesforce with a passkey directly within the app. If your organization requires passkey-based multi-factor authentication for Salesforce, you no longer need to leave the app to complete verification,  it's handled in a native login screen.

Why it matters
Salesforce has been rolling out mandatory passkey verification for certain user roles. This update ensures Impact users can complete that verification smoothly without workarounds or being redirected out of the app.

How to enable it

1. Go to Settings → Pitcher → CRM Integration Settings on your iOS device.
2. Turn on In-App Login Sheet (Passkeys).
3. Restart the app.

This setting is off by default and requires an app restart to take effect.

Requirements

• A passkey already configured for your Salesforce user (e.g., via your organization's password manager).

We've released an updated version of Pitcher Impact for iOS with new features.

• Remaining deferrals on download prompts: When new or updated content is ready, the prompt now shows how many times you can still choose "Later" before a download is required. (Subject to a configuration option, not enabled for all customers by default.)
• Account speciality translations: Account specialities in the planning view now display translated correctly.

Thank you.

We're happy to announce a new version of Pitcher Impact for Android, which includes Salesforce's latest mandatory security updates for Connected Apps and External Client Apps (ECAs).

Background

Salesforce has introduced enhanced OAuth 2.0 security standards for all partner applications integrated with their platform, enforcing PKCE (Proof Key for Code Exchange) and Refresh Token Rotation — mechanisms that protect authentication flows from interception and token misuse. This change is mandatory for all Salesforce-connected applications, including Pitcher Impact

What's New in 3.48.0

Pitcher Impact now fully supports Salesforce's updated OAuth 2.0 requirements:

• PKCE on the authorization code flow used for Salesforce login.
• Refresh Token Rotation, so Pitcher Impact automatically handles rotating refresh tokens issued by Salesforce.

What You Need to Do

Update to Pitcher Impact 3.48.0 as soon as possible. No manual reconfiguration is required on the Pitcher or Salesforce side as it is applied automatically.

We're happy to announce a new version of Pitcher Impact for Windows, which includes Salesforce's latest mandatory security updates for Connected Apps and External Client Apps (ECAs).

Background

Salesforce has introduced enhanced OAuth 2.0 security standards for all partner applications integrated with their platform, enforcing PKCE (Proof Key for Code Exchange) and Refresh Token Rotation — mechanisms that protect authentication flows from interception and token misuse. This change is mandatory for all Salesforce-connected applications, including Pitcher Impact

What's New in 2.138.0

Pitcher Impact now fully supports Salesforce's updated OAuth 2.0 requirements:

• PKCE on the authorization code flow used for Salesforce login.
• Refresh Token Rotation, so Pitcher Impact automatically handles rotating refresh tokens issued by Salesforce.

What You Need to Do

Update to Pitcher Impact 2.138.0 as soon as possible. No manual reconfiguration is required on the Pitcher or Salesforce side as it is applied automatically.

We're happy to announce a new version of Pitcher Impact for iOS, which includes Salesforce's latest mandatory security updates for Connected Apps and External Client Apps (ECAs).

Background

Salesforce has introduced enhanced OAuth 2.0 security standards for all partner applications integrated with their platform, enforcing PKCE (Proof Key for Code Exchange) and Refresh Token Rotation — mechanisms that protect authentication flows from interception and token misuse. This change is mandatory for all Salesforce-connected applications, including Pitcher Impact

What's New in 2.85.1325

Pitcher Impact now fully supports Salesforce's updated OAuth 2.0 requirements:

• PKCE on the authorization code flow used for Salesforce login.
• Refresh Token Rotation, so Pitcher Impact automatically handles rotating refresh tokens issued by Salesforce.

What You Need to Do

Update to Pitcher Impact 2.85.1325 as soon as possible. No manual reconfiguration is required on the Pitcher or Salesforce side as it is applied automatically.