0.4.4

• DevReply.present(category:message:attributes:): message prefills the composer of the new conversation
  (never sent on its own; the user can edit it), attributes go to the team as that conversation's context
  (text, number or true/false; up to 20). Returns false and shows nothing when DevReply isn't configured
  or the chat is switched off; the old present() / present(category:) calls keep compiling.
• await DevReply.deleteUser() never gives up: if DevReply can't be reached, the device forgets the user at
  once and the deletion is retried (with the old install's token, kept in the Keychain) at every launch and
  return to the foreground until the server confirms. true = deleted now, false = queued.
• The chat on/off switch from the dashboard: DevReply.isAvailable. While off, present returns false,
  the unread bubble and banners stay hidden and an open messenger closes; everything else keeps working.
• Events for your analytics: DevReply.addEventListener { event in … } with .messengerOpened,
  .messengerClosed, .conversationStarted(conversationID:category:), .messageSent(conversationID:);
  cancel() the returned subscription to stop.
• Dark mode, opt-in: DevReply.darkTheme = .dark (DevReply's own "Deep blue" look) or a DevReplyTheme with
  your six colours. Without it the chat stays light, exactly as before. Every colour in the chat, its menus and
  pickers, the unread bubble and the in-app banner follows the theme; the category icons have dark artwork.

0.4.3

• Signed-in users: DevReply.login(userID:) after sign-in (your own id for the user; the team sees it, your
  backend can delete the user by it), DevReply.logout() on every sign-out (the device forgets the chat; the
  next person starts empty), await DevReply.deleteUser() in your delete-account flow (deletes the user's
  data, then logs out; false if DevReply couldn't be reached).
• A reinstall starts clean: the Keychain outlives the app, so the SDK forgets the previous install on a
  fresh install.
• Notification taps from a push library (Firebase, expo-notifications, notifee):
  DevReply.handleNotificationOpened(userInfo:) opens the conversation (false for your own). DevReply
  never takes over your notification handling; it handles notifications itself only when the app has no
  UNUserNotificationCenterDelegate. A tap that launches the app opens the conversation once configure runs.
• The privacy manifest declares everything the SDK collects (name, email, user and device ids, photos,
  files, device details, custom attributes) and the UserDefaults reason.

0.4.0

• Replies show who wrote them: the teammate's name, title and photo, once per group of replies.
• The app's icon in the chat's header; the team's faces on the chat's home screen.
• Links from DevReply's emails ("Reply in the app") open the right conversation: DevReply.handle(url).
• A refused public key isn't retried in a loop.
• The chat speaks the user's language (15 languages, the device's by default); DevReply.setLocale("es").
• Reply times are presets, translated in the chat.

DevReply iOS 0.3.2

The chat works inside the new React Native and Flutter packages: the iOS SDK finds its fonts and icons under CocoaPods too, and on Android the unread bubble shows on the current screen when DevReply is configured late, and on plain activities (Flutter). iOS: opening the chat hides the reply banner.

DevReply iOS 0.3.1

Fix: new messages, sent or received, always show above the message field and keyboard. Messages sent in quick succession now arrive in the order they were typed.

DevReply iOS 0.3.0

First public release: home with start buttons, conversations and the chat; photos and files; name first and optional email; "we got it" with the app's reply time; unread indicator. See the README to install. Push notifications, in-app banner and unread bubble included.