我想在我的android应用程序中使用两个不同的后端与不同的响应格式,我正在使用句柄作为依赖注入与网络调用的改进,这是很好的工作。
因为我已经添加了我的第二个服务器网络文件和应用程序模块,它给我的错误在末尾列出。
在这种情况下,我需要知道如何在不做任何显著的架构更改的情况下解决问题。
@Keep
@Module
@InstallIn(SingletonComponent::class)
object AppModule {
@Singleton
@Provides
fun provideRetrofit(gson: Gson,@ApplicationContext appContext: Context): Retrofit = Retrofit.Builder()
.client(
OkHttpClient().newBuilder()
.addInterceptor(HttpLoggingInterceptor().setLevel(HttpLoggingInterceptor.Level.BODY)).readTimeout(80,TimeUnit.SECONDS)
.addInterceptor(
ChuckerInterceptor.Builder(appContext)
.collector(ChuckerCollector(appContext))
.maxContentLength(250000L)
.redactHeaders(emptySet())
.alwaysReadResponseBody(false)
.build()
)
.build()
)
.baseUrl(UtilSingleton.instance!!.GetBaseUrl())
.addConverterFactory(GsonConverterFactory.create(gson))
.build()
@Provides
fun provideGson(): Gson = GsonBuilder().create()
@Provides
fun providePostsService(retrofit: Retrofit): ApiService =
retrofit.create(ApiService::class.java)
@Singleton
@Provides
fun provideApiRemoteDataSource(apiService: ApiService) = ApiRemoteDataSource(apiService)
@Singleton
@Provides
fun provideRepository(
remoteDataSource: ApiRemoteDataSource
) =
MainRepo(remoteDataSource)
/**----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------**/
@Singleton
@Provides
fun provideRetrofitEmall(gson: Gson,@ApplicationContext appContext: Context): Retrofit = Retrofit.Builder()
.client(
OkHttpClient().newBuilder()
.addInterceptor(HttpLoggingInterceptor().setLevel(HttpLoggingInterceptor.Level.BODY)).readTimeout(80,TimeUnit.SECONDS)
.addInterceptor(
ChuckerInterceptor.Builder(appContext)
.collector(ChuckerCollector(appContext))
.maxContentLength(250000L)
.redactHeaders(emptySet())
.alwaysReadResponseBody(false)
.build()
)
.build()
)
.baseUrl(UtilSingleton.instance!!.GetBaseUrl())
.addConverterFactory(GsonConverterFactory.create(gson))
.build()
@Provides
fun providePostsServiceEmall(retrofit: Retrofit): EmallApiService =
retrofit.create(EmallApiService::class.java)
@Singleton
@Provides
fun provideApiRemoteDataSource(apiService: EmallApiService) = EmallApiRemoteDataSource(apiService)
@Singleton
@Provides
fun provideRepository(
remoteDataSource: EmallApiRemoteDataSource
) =
EmallRepo(remoteDataSource)
}
生成错误->
Execution failed for task ':app:kaptLocalDebugKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.gradle.internal.KaptExecution
> java.lang.reflect.InvocationTargetException (no error message)
完整日志->
D:\vaultsNew\vaultspaynewapis\app\build\tmp\kapt3\stubs\localDebug\com\uae\myvaultspay\di\AppModule.java:40: error: Cannot have more than one binding method with the same name in a single module
public final com.uae.myvaultspay.data.remote.ApiRemoteDataSource provideApiRemoteDataSource(@org.jetbrains.annotations.NotNull()
^D:\vaultsNew\vaultspaynewapis\app\build\tmp\kapt3\stubs\localDebug\com\uae\myvaultspay\di\AppModule.java:78: error: Cannot have more than one binding method with the same name in a single module
public final com.uae.myvaultspay.data.remote.emallremote.EmallApiRemoteDataSource provideApiRemoteDataSource(@org.jetbrains.annotations.NotNull()
^D:\vaultsNew\vaultspaynewapis\app\build\tmp\kapt3\stubs\localDebug\com\uae\myvaultspay\di\AppModule.java:48: error: Cannot have more than one binding method with the same name in a single module
public final com.uae.myvaultspay.data.repository.MainRepo provideRepository(@org.jetbrains.annotations.NotNull()
^D:\vaultsNew\vaultspaynewapis\app\build\tmp\kapt3\stubs\localDebug\com\uae\myvaultspay\di\AppModule.java:86: error: Cannot have more than one binding method with the same name in a single module
public final com.uae.myvaultspay.data.repository.EmallRepo provideRepository(@org.jetbrains.annotations.NotNull()
^warning:
File for type 'com.uae.myvaultspay.MyApplication_HiltComponents' created
in the last round will not be subject to annotation processing.
Execution failed for task ':app:kaptLocalDebugKotlin'.
> A failure occurred while executing
org.jetbrains.kotlin.gradle.internal.KaptExecution
> java.lang.reflect.InvocationTargetException (no error message)
发布于 2021-08-05 04:50:46
如果您想使用Dagger或Hilt返回Retrofit client,那么您应该使用@Named
注释。此注释帮助Hilt或Dagger理解具有相同Retrofit返回类型的您,您需要获取哪个Retrofit实例。
按照下面的方法,您可以提供多个带柄或短剑的改装实例。
首先,我在这里看到您提供了2个改造实例。为您提供的每个改造实例放置@Named
注释。
object AppModule {
@Singleton
@Provides
@Named("Normal")
fun provideRetrofit(gson: Gson, @ApplicationContext appContext: Context): Retrofit = ...
@Singleton
@Provides
@Named("Email")
fun provideRetrofitEmall(gson: Gson, @ApplicationContext appContext: Context): Retrofit = ...
}
接下来,当您提供api服务时,向Hilt或Dagger指定它需要哪个改装实例。
object AppModule {
@Provides
fun providePostsService(@Named("Normal") retrofit: Retrofit): ApiService = retrofit.create(ApiService::class.java)
@Provides
fun providePostsServiceEmall(@Named("Email") retrofit: Retrofit): EmallApiService = retrofit.create(EmallApiService::class.java)
}
最后,清理项目并重新构建项目以查看结果。
https://stackoverflow.com/questions/68666532
复制