Device Settings, Intercom Integration and Improvements #902
Conversation
|
WalkthroughThis pull request introduces significant changes to the Flutter app's UI, navigation flow, and device settings management. It also updates the Android and iOS build configurations, integrates Intercom for chat support and push notifications, and adds environment variables for Intercom configuration. Changes
Uplevel your code reviews with Entelligence.AI ProEntelligence.AI ProIf you like this project, please support us by purchasing the Pro version. The Pro version has advanced context, superior noise reduction and several proprietary improvements compared to the open source version. Moreover, Entelligence.AI Pro is free for open source projects. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Files selected (8)
- app/lib/pages/capture/connect.dart (2)
- app/lib/pages/home/device.dart (3)
- app/lib/pages/home/device_settings.dart (1)
- app/lib/pages/home/support.dart (2)
- app/lib/pages/settings/device_settings.dart (1)
- app/lib/pages/settings/page.dart (2)
- app/lib/pages/settings/widgets/expansion_tile_card.dart (1)
- app/lib/providers/device_provider.dart (2)
Files skipped from review due to trivial changes (2)
- app/lib/pages/home/support.dart
- app/lib/pages/settings/page.dart
Review comments generated (12)
- Review: 9
- LGTM: 3
Tips
Chat with Entelligence.AI Bot (@Entelligence.AI)
- Reply on review comments left by this bot to ask follow-up questions. A review comment is a comment on a diff or a file.
- Invite the bot into a review comment chain by tagging
@Entelligence.AIin a reply.
Code suggestions
- The bot may make code suggestions, but please review them carefully before committing since the line number ranges may be misaligned.
- You can edit the comment made by the bot and manually tweak the suggestion if it is slightly off.
Pausing incremental reviews
- Add
@Entelligence.AI: ignoreanywhere in the PR description to pause further reviews from the bot.
| @@ -1,5 +1,5 @@ | |||
| import 'package:flutter/material.dart'; | |||
| import 'package:friend_private/pages/home/device_settings.dart'; | |||
| import 'package:friend_private/pages/settings/device_settings.dart'; | |||
There was a problem hiding this comment.
The import path for DeviceSettings has been updated. Ensure that the new path 'package:friend_private/pages/settings/device_settings.dart' is correct and the file exists at this location.
- import 'package:friend_private/pages/home/device_settings.dart';
+ import 'package:friend_private/pages/settings/device_settings.dart';| builder: (context) => const DeviceSettings( | ||
| isDeviceConnected: false, | ||
| ), | ||
| builder: (context) => const DeviceSettings(), |
There was a problem hiding this comment.
The instantiation of DeviceSettings no longer includes the isDeviceConnected parameter. If this parameter was used to control any logic within DeviceSettings, ensure that its removal doesn't cause any unintended behavior.
- builder: (context) => const DeviceSettings(isDeviceConnected: false),
+ builder: (context) => const DeviceSettings(),
app/lib/pages/home/device.dart
Outdated
| const SizedBox(height: 8), | ||
| TextButton( | ||
| onPressed: () { | ||
| routeToPage(context, const DeviceSettings()); | ||
| }, | ||
| child: const Text( | ||
| 'How to charge?', | ||
| style: TextStyle( | ||
| color: Colors.white, | ||
| decoration: TextDecoration.underline, | ||
| ), | ||
| ), | ||
| ), |
There was a problem hiding this comment.
A new TextButton has been added to navigate to the DeviceSettings page when clicked. However, it seems like there's no parameter passed to DeviceSettings(). If DeviceSettings requires any mandatory parameters, this will cause an error. Please ensure that all required parameters are passed correctly.
- routeToPage(context, const DeviceSettings());
+ routeToPage(context, DeviceSettings(device: widget.device));| // TODO: thinh, use connection directly | ||
| Future _bleDisconnectDevice(BTDeviceStruct btDevice) async { | ||
| var connection = await ServiceManager.instance().device.ensureConnection(btDevice.id); | ||
| if (connection == null) { | ||
| return Future.value(null); | ||
| } | ||
| return await connection.disconnect(); | ||
| } |
There was a problem hiding this comment.
The _bleDisconnectDevice method is using a direct connection to disconnect the device. This could lead to issues if the connection is not properly managed or if there are multiple connections to the same device. It would be better to use a centralized service for managing device connections, which can ensure that connections are properly handled and prevent potential issues with multiple connections.
- Future _bleDisconnectDevice(BTDeviceStruct btDevice) async {
- var connection = await ServiceManager.instance().device.ensureConnection(btDevice.id);
- if (connection == null) {
- return Future.value(null);
- }
- return await connection.disconnect();
- }
+ Future _bleDisconnectDevice(BTDeviceStruct btDevice) async {
+ await ServiceManager.instance().device.disconnectDevice(btDevice.id);
+ }| onPressed: () async { | ||
| await SharedPreferencesUtil().btDeviceStructSet(BTDeviceStruct(id: '', name: '')); | ||
| SharedPreferencesUtil().deviceName = ''; | ||
| if (provider.connectedDevice != null) { | ||
| await _bleDisconnectDevice(provider.connectedDevice!); | ||
| } | ||
| provider.setIsConnected(false); | ||
| provider.setConnectedDevice(null); | ||
| provider.updateConnectingStatus(false); | ||
| context.read<OnboardingProvider>().stopFindDeviceTimer(); | ||
| Navigator.of(context).pop(); | ||
| Navigator.of(context).pop(); | ||
| ScaffoldMessenger.of(context).showSnackBar(SnackBar( | ||
| content: Text( | ||
| 'Your Friend is ${provider.connectedDevice == null ? "unpaired" : "disconnected"} 😔'), | ||
| )); | ||
| MixpanelManager().disconnectFriendClicked(); | ||
| }, |
There was a problem hiding this comment.
This block of code seems to be doing a lot of operations related to disconnecting a device. It might be more maintainable and easier to understand if these operations were encapsulated into a single method within the DeviceProvider class. This way, you can just call that method here, making the code cleaner and easier to read.
- await SharedPreferencesUtil().btDeviceStructSet(BTDeviceStruct(id: '', name: ''));
- SharedPreferencesUtil().deviceName = '';
- if (provider.connectedDevice != null) {
- await _bleDisconnectDevice(provider.connectedDevice!);
- }
- provider.setIsConnected(false);
- provider.setConnectedDevice(null);
- provider.updateConnectingStatus(false);
- context.read<OnboardingProvider>().stopFindDeviceTimer();
+ await provider.disconnectDevice();In the DeviceProvider class, you can add a new method:
Future<void> disconnectDevice() async {
await SharedPreferencesUtil().btDeviceStructSet(BTDeviceStruct(id: '', name: ''));
SharedPreferencesUtil().deviceName = '';
if (connectedDevice != null) {
await _bleDisconnectDevice(connectedDevice!); // Assuming _bleDisconnectDevice is moved to DeviceProvider
}
setIsConnected(false);
setConnectedDevice(null);
updateConnectingStatus(false);
context.read<OnboardingProvider>().stopFindDeviceTimer(); // This might need to be handled differently depending on your app's architecture
}
mdmohsin7
changed the title
There was a problem hiding this comment.
Files selected (16)
- app/android/app/build.gradle (3)
- app/android/app/proguard-rules.pro (1)
- app/android/build.gradle (2)
- app/android/gradle/wrapper/gradle-wrapper.properties (1)
- app/android/settings.gradle (1)
- app/ios/Podfile (1)
- app/ios/Runner.xcodeproj/project.pbxproj (9)
- app/ios/Runner/Info.plist (1)
- app/lib/env/dev_env.dart (1)
- app/lib/env/env.dart (2)
- app/lib/env/prod_env.dart (1)
- app/lib/main.dart (4)
- app/lib/pages/home/device.dart (3)
- app/lib/pages/settings/device_settings.dart (1)
- app/lib/pages/settings/page.dart (3)
- app/lib/providers/device_provider.dart (2)
Files ignored due to filter (1)
- app/pubspec.yaml
Files skipped from review due to trivial changes (5)
- app/android/app/proguard-rules.pro
- app/android/build.gradle
- app/android/gradle/wrapper/gradle-wrapper.properties
- app/android/settings.gradle
- app/ios/Podfile
Review comments generated (33)
- Review: 18
- LGTM: 15
Tips
Chat with Entelligence.AI Bot (@Entelligence.AI)
- Reply on review comments left by this bot to ask follow-up questions. A review comment is a comment on a diff or a file.
- Invite the bot into a review comment chain by tagging
@Entelligence.AIin a reply.
Code suggestions
- The bot may make code suggestions, but please review them carefully before committing since the line number ranges may be misaligned.
- You can edit the comment made by the bot and manually tweak the suggestion if it is slightly off.
Pausing incremental reviews
- Add
@Entelligence.AI: ignoreanywhere in the PR description to pause further reviews from the bot.
| @@ -445,7 +445,7 @@ | |||
| CODE_SIGN_ENTITLEMENTS = "Runner/RunnerDebug-prod.entitlements"; | |||
| DEVELOPMENT_TEAM = 9536L8KLMP; | |||
| INFOPLIST_KEY_CFBundleDisplayName = Omi; | |||
| IPHONEOS_DEPLOYMENT_TARGET = 14.0; | |||
| IPHONEOS_DEPLOYMENT_TARGET = 15.0; | |||
There was a problem hiding this comment.
The iOS deployment target has been updated from 14.0 to 15.0. This change will require all users to have at least iOS 15.0 installed on their devices to use the app. If there are still a significant number of users on iOS 14, this could potentially exclude them from being able to update or install the app. Please ensure that this change aligns with your user base and support strategy.
- IPHONEOS_DEPLOYMENT_TARGET = 14.0;
+ IPHONEOS_DEPLOYMENT_TARGET = 15.0;| namespace "com.friend.ios" | ||
|
|
||
|
|
There was a problem hiding this comment.
The namespace "com.friend.ios" seems to be added in the Android build.gradle file. This could potentially cause confusion as it's an iOS namespace being used in an Android context. If this is intentional and required for some reason, consider adding a comment explaining why this is necessary.
- namespace "com.friend.ios"
+ // Using iOS namespace due to XYZ reason
+ namespace "com.friend.ios"| dependencies { | ||
| implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.8.10" | ||
| androidTestImplementation 'androidx.test:runner:1.2.0' | ||
| androidTestImplementation 'androidx.test.espresso:espresso-core:3.2.0' | ||
| implementation 'androidx.multidex:multidex:2.0.1' |
There was a problem hiding this comment.
The Kotlin dependency has been removed from the dependencies block. If Kotlin is no longer being used in the project, this is fine. However, if there are still parts of the project written in Kotlin, this will cause compilation errors. Please ensure that all Kotlin code has been properly migrated to Java or another language before removing this dependency.
| @@ -2,6 +2,7 @@ import 'package:flutter/material.dart'; | |||
| import 'package:friend_private/backend/auth.dart'; | |||
| import 'package:friend_private/backend/preferences.dart'; | |||
| import 'package:friend_private/main.dart'; | |||
| import 'package:friend_private/pages/home/support.dart'; | |||
There was a problem hiding this comment.
The import statement for SupportPage has been added. Ensure that the SupportPage is properly implemented and does not have any dependencies that could potentially break the application.
+ import 'package:friend_private/pages/home/support.dart';| @@ -13,6 +14,8 @@ import 'package:friend_private/utils/other/temp.dart'; | |||
| import 'package:friend_private/widgets/dialog.dart'; | |||
| import 'package:package_info_plus/package_info_plus.dart'; | |||
|
|
|||
| import 'device_settings.dart'; | |||
There was a problem hiding this comment.
The import statement for DeviceSettings has been added. Make sure that DeviceSettings is correctly implemented and doesn't introduce any unwanted dependencies that could affect the stability of the application.
+ import 'device_settings.dart';| const SizedBox(height: 8), | ||
| TextButton( | ||
| onPressed: () async { | ||
| await Intercom.instance.displayArticle('9907475-how-to-charge-the-device'); | ||
| }, | ||
| child: const Text( | ||
| 'How to charge?', | ||
| style: TextStyle( | ||
| color: Colors.white, | ||
| decoration: TextDecoration.underline, | ||
| ), | ||
| ), | ||
| ), |
There was a problem hiding this comment.
The addition of a TextButton that opens an Intercom article when pressed seems to be a good way to provide users with additional information. However, ensure that the hardcoded article ID '9907475-how-to-charge-the-device' is valid and the article content is up-to-date.
+ const SizedBox(height: 8),
+ TextButton(
+ onPressed: () async {
+ await Intercom.instance.displayArticle('9907475-how-to-charge-the-device');
+ },
+ child: const Text(
+ 'How to charge?',
+ style: TextStyle(
+ color: Colors.white,
+ decoration: TextDecoration.underline,
+ ),
+ ),
+ ),
],
),
);| Future _bleDisconnectDevice(BTDeviceStruct btDevice) async { | ||
| var connection = await ServiceManager.instance().device.ensureConnection(btDevice.id); | ||
| if (connection == null) { | ||
| return Future.value(null); | ||
| } | ||
| return await connection.disconnect(); | ||
| } |
There was a problem hiding this comment.
The _bleDisconnectDevice function does not handle the case when connection is null. It should throw an error or return a specific result indicating that the connection could not be established.
if (connection == null) {
return Future.value(null);
}
+ else {
+ throw Exception('Unable to establish connection with device');
+ }
return await connection.disconnect();| WidgetsBinding.instance.addPostFrameCallback((_) { | ||
| context.read<DeviceProvider>().getDeviceInfo(); | ||
| }); |
There was a problem hiding this comment.
It's good practice to call super.initState() at the beginning of initState. This ensures that any code from the superclass is executed before your subclass code.
WidgetsBinding.instance.addPostFrameCallback((_) {
context.read<DeviceProvider>().getDeviceInfo();
});
- super.initState();
+ super.initState();| await SharedPreferencesUtil().btDeviceStructSet(BTDeviceStruct(id: '', name: '')); | ||
| SharedPreferencesUtil().deviceName = ''; | ||
| if (provider.connectedDevice != null) { | ||
| await _bleDisconnectDevice(provider.connectedDevice!); | ||
| } | ||
| provider.setIsConnected(false); | ||
| provider.setConnectedDevice(null); | ||
| provider.updateConnectingStatus(false); | ||
| context.read<OnboardingProvider>().stopFindDeviceTimer(); | ||
| Navigator.of(context).pop(); | ||
| Navigator.of(context).pop(); | ||
| ScaffoldMessenger.of(context).showSnackBar(SnackBar( | ||
| content: Text( | ||
| 'Your Friend is ${provider.connectedDevice == null ? "unpaired" : "disconnected"} 😔'), | ||
| )); | ||
| MixpanelManager().disconnectFriendClicked(); | ||
| }, |
There was a problem hiding this comment.
This block of code seems to be doing a lot of operations related to disconnecting a device. Consider moving this logic into a separate method in the DeviceProvider class to improve readability and maintainability.
- await SharedPreferencesUtil().btDeviceStructSet(BTDeviceStruct(id: '', name: ''));
- SharedPreferencesUtil().deviceName = '';
- if (provider.connectedDevice != null) {
- await _bleDisconnectDevice(provider.connectedDevice!);
- }
- provider.setIsConnected(false);
- provider.setConnectedDevice(null);
- provider.updateConnectingStatus(false);
- context.read<OnboardingProvider>().stopFindDeviceTimer();
- Navigator.of(context).pop();
- Navigator.of(context).pop();
- ScaffoldMessenger.of(context).showSnackBar(SnackBar(
- content: Text(
- 'Your Friend is ${provider.connectedDevice == null ? "unpaired" : "disconnected"} 😔'),
- ));
- MixpanelManager().disconnectFriendClicked();
+ provider.disconnectDevice();| List<Widget> deviceSettingsWidgets(DeviceInfo? deviceInfo, BTDeviceStruct? device, BuildContext context) { | ||
| return [ | ||
| ListTile( | ||
| title: const Text('Device Name'), | ||
| subtitle: Text(device?.name ?? 'Friend'), | ||
| ), | ||
| ListTile( | ||
| title: const Text('Device ID'), | ||
| subtitle: Text(device?.id ?? '12AB34CD:56EF78GH'), | ||
| ), | ||
| GestureDetector( | ||
| onTap: () { | ||
| Navigator.push( | ||
| context, | ||
| MaterialPageRoute( | ||
| builder: (context) => FirmwareUpdate( | ||
| deviceInfo: deviceInfo!, | ||
| device: device, | ||
| ), | ||
| ), | ||
| ); | ||
| }, | ||
| child: ListTile( | ||
| title: const Text('Firmware Update'), | ||
| subtitle: Text(deviceInfo?.firmwareRevision ?? '1.0.2'), | ||
| trailing: const Icon(Icons.arrow_forward_ios), | ||
| ), | ||
| ), | ||
| ListTile( | ||
| title: const Text('Hardware Revision'), | ||
| subtitle: Text(deviceInfo?.hardwareRevision ?? 'XIAO'), | ||
| ), | ||
| ListTile( | ||
| title: const Text('Model Number'), | ||
| subtitle: Text(deviceInfo?.modelNumber ?? 'Friend'), | ||
| ), | ||
| ListTile( | ||
| title: const Text('Manufacturer Name'), | ||
| subtitle: Text(deviceInfo?.manufacturerName ?? 'Based Hardware'), | ||
| ), | ||
| ]; | ||
| } |
There was a problem hiding this comment.
The deviceSettingsWidgets function is tightly coupled with the UI. Consider moving this logic into a separate widget to improve modularity and testability.
- List<Widget> deviceSettingsWidgets(DeviceInfo? deviceInfo, BTDeviceStruct? device, BuildContext context) {
- return [
- ListTile(
- title: const Text('Device Name'),
- subtitle: Text(device?.name ?? 'Friend'),
- ),
- ListTile(
- title: const Text('Device ID'),
- subtitle: Text(device?.id ?? '12AB34CD:56EF78GH'),
- ),
- GestureDetector(
- onTap: () {
- Navigator.push(
- context,
- MaterialPageRoute(
- builder: (context) => FirmwareUpdate(
- deviceInfo: deviceInfo!,
- device: device,
- ),
- ),
- );
- },
- child: ListTile(
- title: const Text('Firmware Update'),
- subtitle: Text(deviceInfo?.firmwareRevision ?? '1.0.2'),
- trailing: const Icon(Icons.arrow_forward_ios),
- ),
- ),
- ListTile(
- title: const Text('Hardware Revision'),
- subtitle: Text(deviceInfo?.hardwareRevision ?? 'XIAO'),
- ),
- ListTile(
- title: const Text('Model Number'),
- subtitle: Text(deviceInfo?.modelNumber ?? 'Friend'),
- ),
- ListTile(
- title: const Text('Manufacturer Name'),
- subtitle: Text(deviceInfo?.manufacturerName ?? 'Based Hardware'),
- ),
- ];
- }
+ DeviceSettingsWidget(deviceInfo: deviceInfo, device: device);
There was a problem hiding this comment.
Files selected (6)
- app/android/app/build.gradle (4)
- app/android/app/proguard-rules.pro (2)
- app/android/app/src/main/AndroidManifest.xml (1)
- app/android/app/src/main/java/com/friend/ios/MyApp.kt (1)
- app/lib/pages/settings/page.dart (3)
- app/lib/services/notification_service.dart (2)
Files skipped from review due to trivial changes (1)
- app/lib/pages/settings/page.dart
Review comments generated (10)
- Review: 7
- LGTM: 3
Tips
Chat with Entelligence.AI Bot (@Entelligence.AI)
- Reply on review comments left by this bot to ask follow-up questions. A review comment is a comment on a diff or a file.
- Invite the bot into a review comment chain by tagging
@Entelligence.AIin a reply.
Code suggestions
- The bot may make code suggestions, but please review them carefully before committing since the line number ranges may be misaligned.
- You can edit the comment made by the bot and manually tweak the suggestion if it is slightly off.
Pausing incremental reviews
- Add
@Entelligence.AI: ignoreanywhere in the PR description to pause further reviews from the bot.
| # For Awesome Notification Plugin | ||
| -keep class com.google.common.reflect.TypeToken | ||
| -keep class * extends com.google.common.reflect.TypeToken | ||
|
|
There was a problem hiding this comment.
The Proguard rules for the Awesome Notification Plugin are added, but it's not clear if this plugin is used in the project. If it's not used, these lines should be removed to avoid unnecessary rules.
- # For Awesome Notification Plugin
- -keep class com.google.common.reflect.TypeToken
- -keep class * extends com.google.common.reflect.TypeTokenIf the plugin is indeed used, then this change is fine.
| @@ -67,6 +67,7 @@ | |||
|
|
|||
| <!-- Add android:stopWithTask option only when necessary. --> | |||
| <application | |||
| android:name=".MyApp" | |||
There was a problem hiding this comment.
The android:name attribute has been added to the <application> tag in the AndroidManifest.xml file. This is used to specify a fully qualified class name that extends Application, which will be instantiated when your process is created. Here, it's set to .MyApp.
Please ensure that the MyApp class exists and extends from the Application class. Also, if there are any global state or singleton instances being initialized in this class, make sure they are thread-safe and properly managed to avoid memory leaks.
- <application
+ <application
+ android:name=".MyApp"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:requestLegacyExternalStorage="true"| @@ -124,6 +125,7 @@ class NotificationService { | |||
| if (token == null) return; | |||
| String timeZone = await getTimeZone(); | |||
| if (FirebaseAuth.instance.currentUser != null && token.isNotEmpty) { | |||
| await Intercom.instance.sendTokenToIntercom(token); | |||
There was a problem hiding this comment.
The sendTokenToIntercom method from the Intercom instance is being called with the FCM token as an argument. This is used to register the device's FCM token with Intercom, enabling push notifications.
+ await Intercom.instance.sendTokenToIntercom(token);However, it would be a good idea to add error handling here. If the Intercom service fails or there's a network issue, this could throw an exception which isn't currently being caught.
try {
await Intercom.instance.sendTokenToIntercom(token);
} catch (e) {
print('Failed to send FCM token to Intercom: $e');
}This will ensure that any issues with sending the token to Intercom don't cause the entire function to fail and provide some debugging information if something goes wrong.
| buildFeatures { | ||
| buildConfig = true | ||
| } | ||
|
|
||
| namespace "com.friend.ios" | ||
|
|
||
|
|
There was a problem hiding this comment.
The buildFeatures block and the namespace field have been added. The buildFeatures block is used to enable or disable specific build features. Here, buildConfig is set to true which means a BuildConfig class will be generated in your APK file. This class contains constants that are useful at runtime for your app.
The namespace field is used to specify the package name for the generated R.java and Manifest.java files. It's good to see that you've specified it here, but make sure that this namespace matches with your application's package name.
+ buildFeatures {
+ buildConfig = true
+ }
+
+ namespace "com.friend.ios"| buildConfigField("String", "INTERCOM_APP_ID", "\"${System.getenv("intercom.app.id")}\"") | ||
| buildConfigField("String", "INTERCOM_ANDROID_API_KEY", "\"${System.getenv("intercom.android.api.key")}\"") |
There was a problem hiding this comment.
You're using environment variables to store sensitive data such as the Intercom App ID and API key. This is a good practice as it keeps these values out of the codebase, reducing the risk of accidental exposure. However, ensure that these environment variables are properly set in the build environment where this code will run.
+ buildConfigField("String", "INTERCOM_APP_ID", "\"${System.getenv("intercom.app.id")}\"")
+ buildConfigField("String", "INTERCOM_ANDROID_API_KEY", "\"${System.getenv("intercom.android.api.key")}\"")| @@ -105,6 +114,7 @@ android { | |||
| shrinkResources true | |||
| } | |||
| debug{ | |||
| proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' | |||
There was a problem hiding this comment.
You've added ProGuard rules file to the debug build type. While this is not an issue per se, it's unusual to use ProGuard in debug builds as it obfuscates the code, making debugging more difficult. If you have a specific reason for doing this, it's fine. Otherwise, consider removing it from the debug build type.
+ proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'| androidTestImplementation 'androidx.test:runner:1.2.0' | ||
| androidTestImplementation 'androidx.test.espresso:espresso-core:3.2.0' | ||
| implementation 'androidx.multidex:multidex:2.0.1' | ||
| implementation 'com.squareup.okhttp3:okhttp:4.12.0' | ||
| implementation 'androidx.constraintlayout:constraintlayout:2.0.0-alpha3' | ||
| implementation 'io.intercom.android:intercom-sdk:latest.release' |
There was a problem hiding this comment.
You've added new dependencies and removed the Kotlin standard library dependency. The Intercom SDK has been added for chat support, which aligns with the PR description. However, the removal of the Kotlin standard library might cause issues if there are any Kotlin files in your project. If you're not using Kotlin at all, then it's fine to remove this dependency.
- implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.8.10"
+ implementation 'androidx.constraintlayout:constraintlayout:2.0.0-alpha3'
+ implementation 'io.intercom.android:intercom-sdk:latest.release'
need help? chat with usoption at the top in settingsScreenRecording_09-23-2024.12-20-12_1.1.mp4
Summary by Entelligence.AI
DeviceSettingswidget, improving code modularity.SupportPagewithExpansionTileCardfor better presentation of firmware updates and bootloader support information. Added links to guides for manual firmware and bootloader updates.