🔄 Migration guide: 1.0 → 1.1

This guide lists only what changed between the 1.0.0 and 1.1.0 documentation releases.

Unchanged in 1.1

If you already integrated per 1.0.0 quick-start / initialization docs, you already use initialize → connect / connectUser with JWT + gender + height + weight (no separate userId). You do not need to rework that flow.

---

Summary

Area	1.0.0 docs	1.1.0 change
Lifecycle	initialize → connectUser / connect	No change
Android imports	com.azeoo.sdk.*	com.azeoo.sdk.core.* + ProGuard
Android init	theme, deepLinks, safeArea	+ optional environment, connector
iOS AzeooConfig	locale, analytics, offline, timeout	+ logLevel; connector at init
React Native AzeooProvider	userId, authToken, autoConnect	Removed — call useAzeoo().connect()
Flutter embed	buildNutritionMainScreen() in examples	Prefer AzeooSDKContent
Flutter module nav	showDiary, showScanner, showSearch	Renamed to actual API methods (see below)
New (documented)	—	setClubId, AzeooScreens, AzeooSDKListener

---

Android

Update imports and ProGuard

1.0.0

import com.azeoo.sdk.AzeooSDK
import com.azeoo.sdk.AzeooConfig

1.1.0

import com.azeoo.sdk.core.AzeooSDK
import com.azeoo.sdk.core.AzeooConfig

ProGuard — replace com.azeoo.sdk.** with:

-keep class com.azeoo.sdk.core.** { *; }
-keep interface com.azeoo.sdk.core.** { *; }
-dontwarn com.azeoo.sdk.core.**

Your initialize / connectUser calls stay the same if they matched the 1.0.0 quick-start.

Optional new init parameters

AzeooSDK.initialize(
    context = applicationContext,
    apiKey = apiKey,
    environment = "production", // new — or "staging"
    connector = AzeooConnectorConfig.azeoo(clubId = 123L), // new — if your key uses connectors
    // … existing config, theme, deepLinks, safeArea
) { error -> /* … */ }

New APIs (optional)

• setClubId(clubId) — switch club for azeoo connector without disconnect
• AzeooSDK.shared.listener — AzeooSDKListener for Flutter → native events
• sdk.modules.screens — embed standalone screens (recipe, plan, etc.)

---

iOS

AzeooConfig — add logLevel

1.0.0

let config = AzeooConfig(
    locale: "en",
    analyticsEnabled: true,
    offlineEnabled: true,
    connectionTimeoutSeconds: 30
)

1.1.0

let config = AzeooConfig(
    locale: "en",
    analyticsEnabled: true,
    offlineEnabled: true,
    connectionTimeoutSeconds: 30,
    logLevel: .warning  // new
)

Pass connector: to AzeooSDK.initialize if your API key requires it — see Connectors.

connectUser signature is unchanged from 1.0.0.

---

Flutter

Embedding — prefer AzeooSDKContent

1.0.0 quick-start used the example helper:

buildNutritionMainScreen(bottomSafeArea: false);

1.1.0 — use the public embed widget:

import 'package:azeoo_sdk/core/app/azeoo_sdk_content.dart';

Scaffold(body: AzeooSDKContent(bottomSafeArea: false))

initialize, connect, and AzeooSDKModules imperative navigation are unchanged.

Navigation method names (doc corrections)

If you copied method names from the 1.0.0 Flutter navigation page, update to the real API:

1.0.0 doc (incorrect)	1.1.0 (actual)
showDiary()	showMainScreen()
showScanner(…)	showBarcodeScanner() / showMobileScanner()
showSearch()	showNutritionSearch()
showRecipe(42, …)	showRecipe('recipe-id')

---

React Native

This is the main integration change if you used AzeooProvider as documented in 1.0.0.

1.0.0

<AzeooProvider
  apiKey={API_KEY}
  userId={userId}
  authToken={jwt}
  autoConnect={true}
  …
>

1.1.0 — provider initializes only; connect after login:

import { AzeooProvider, useAzeoo } from 'react-native-azeoo-lib';

function LoginScreen() {
  const { connect, isInitialized } = useAzeoo();

  const onLogin = async (jwt: string) => {
    if (!isInitialized) return;
    await connect(jwt, gender, height, weight);
  };
}

Remove userId, authToken, and autoConnect props from AzeooProvider.

Direct AzeooSDK.initialize + AzeooSDK.connect (1.0.0 quick-start) is unchanged.

---

Next steps

• Changelog
• 1.1.0 Initialization
• Platform Quick start