Repository navigation
Check before you upgrade. Four changes behave differently with no code change on your side: the one-argument configure(with:) now talks to production, a feedback row on iOS and visionOS loses its "⋯" button, the moderation contact moves into the list as its last row, and the Showcase vote count no longer uses tabular digits. Each is described below. Nothing is removed or renamed.
Added
FeedbackListView(…, title:)(defaultnil, which keeps the localized "Feedback"): the text on the list's navigation bar. AnavigationTitleapplied outside the view does not replace the list's own. Pass text already localized for your app.SwiftlyFeedback.registerPayment(_:): anasync throwsway to send a payment, ornilto clear it, and find out whether the server stored it.updateUser(payment:)still returns nothing and only logs a failure, such as a 401 for a bad key.SwiftlyFeedbackTheme.voteCountOnPrimaryColorandvoteCountColor: the Showcase vote count's colour on a voted and an unvoted capsule. The defaults, white and your primary color, look the same as before. Set them when your primary color is too light for white text.deleteComment(_:from:): deletes the current user's own comment. The server refuses another user's comment or a staff reply.
Changed
- A feedback row has one trailing affordance on iOS and visionOS. The list's disclosure indicator stays and the row's "⋯" button is gone. Report and Block moved to the row's context menu (touch and hold), and stay in the detail screen's toolbar. macOS is unchanged.
- The list's search field uses the system's "Search" prompt. "Search Feedback" clipped at larger text in the width of iPad's list column.
⚠️ Behaviour change:SwiftlyFeedback.configure(with:)now talks to production. The one-argument call used to send your API key tohttp://localhost:8080and now useshttps://api.prod.getfeedbackkit.com, as the JavaScript, Flutter and Kotlin SDKs do. If you develop against a local server with this call, change it toSwiftlyFeedback.configure(environment: .local, key: "your_key"), or your local builds will reach production.configure(with:baseURL:),configure(environment:key:)andconfigureAutoare unchanged.- The Showcase vote count no longer uses tabular digits. Digit widths in the count can differ slightly from before, so a count can shift by a fraction of a point when it changes. The accessibility contrast audit failed the count while it used them. On macOS, the time under a comment bubble no longer uses them either.
Fixed
- Listing feedback or comments can no longer send requests without end when a proxy or cache returns a stale or incomplete page. If a later page's number is missing or is not the page requested, the list stops and returns the rows it already has, and it never follows more than 100 further pages. When either happens, the SDK logs one warning with the path and the two page numbers.
- The moderation contact no longer sits on top of rows. A populated list now shows it as its last row, so it scrolls with the rows and clears the tab bar. Screens with no rows still pin it at the bottom. Its text is also darker, with the address underlined, to pass the contrast audit.
- macOS accessibility. The list's outline and comment field have names, and a row's link reports a role.
- A second vote tap no longer races the first. The list and the detail screen ignore further taps on an item until its vote request finishes. If the server answers 409 because the vote already exists, the item refreshes instead of showing an error.
- macOS feedback detail accessibility. A comment bubble now reports a role and keeps its "sender, text, time" name. The status name, category and date in the header use the primary text colour, to pass the contrast audit.
- macOS submit form. The small notes under the fields use the primary text colour, to pass the contrast audit. iOS and visionOS are unchanged.