Jump to content
jamesphw

Bug: Unable to Use Identify Feature When Media Has Multiple Versions

Recommended Posts

jamesphw

Currently, the identify feature fails when you have multiple versions of the same media file (e.g. a 720p and 1080p version). In particular I am trying to use an IMDB identifier, but I'm not sure if that makes the difference. I can consistently reproduce on all media where there are multiple versions.

 

Here is the server log snippet:

 

2020-05-31 15:40:36.651 Error HttpServer: Error processing request
*** Error Report ***
Version: 4.4.2.0
Command line: /data/app/com.emby.embyserver-mMCyeOMtuZgjrEQh9s24BA==/base.apk
Operating system: Unix 4.9.140.72
64-Bit OS: True
64-Bit Process: True
User Interactive: False
Runtime: file:///mscorlib.dll
System.Environment.Version: 4.0.50524.0
Processor count: 4
Program data path: /storage/emulated/0/Android/data/com.emby.embyserver/files
Application directory: /data/user/0/com.emby.embyserver
Mono: 6.8.0 (2019-10/c0c5c78e2bd)
Android Version: 9-REL - Base:  - SDK: P
Build ID: PPR1.180610.011 - Incremental: 4086637_1873.3004 Patch-Level: 2019-11-05
Fingerprint: NVIDIA/darcy/darcy:9/PPR1.180610.011/4086637_1873.3004:user/release-keys
Model: SHIELD Android TV - NVIDIA/NVIDIA
Hardware: darcy/darcy/darcy/darcy
SupportedAbis: arm64-v8a, armeabi-v7a, armeabi
SQLitePCL.pretty.SQLiteException: Constraint: FOREIGN KEY constraint failed
SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown.
  at SQLitePCL.pretty.SQLiteException.CheckOk (SQLitePCL.sqlite3 db, System.Int32 rc) [0x00017] in <43c671a5dd5a41e4b82909d3de8c3eb4>:0 
  at SQLitePCL.pretty.SQLiteException.CheckOk (SQLitePCL.sqlite3_stmt stmt, System.Int32 rc) [0x00006] in <43c671a5dd5a41e4b82909d3de8c3eb4>:0 
  at SQLitePCL.pretty.StatementImpl.MoveNext () [0x0004a] in <43c671a5dd5a41e4b82909d3de8c3eb4>:0 
  at Emby.Server.Implementations.Data.SqliteItemRepository.InsertItemLinks (System.Int64 internalId, System.Int64 topParentId, System.Collections.Generic.List`1[T] values, SQLitePCL.pretty.IDatabaseConnection db) [0x000f8] in <4678cc7d86684b659921915f01406e6d>:0 
  at Emby.Server.Implementations.Data.SqliteItemRepository.UpdateItemLinks (System.Int64 internalId, System.Int64 topParentId, System.Collections.Generic.List`1[T] values, SQLitePCL.pretty.IDatabaseConnection db) [0x0004a] in <4678cc7d86684b659921915f01406e6d>:0 
  at Emby.Server.Implementations.Data.SqliteItemRepository.SaveItemsInTranscation (SQLitePCL.pretty.IDatabaseConnection db, System.Collections.Generic.List`1[T] tuples) [0x0011d] in <4678cc7d86684b659921915f01406e6d>:0 
  at Emby.Server.Implementations.Data.SqliteItemRepository.SaveItems (System.Collections.Generic.List`1[T] items, System.Threading.CancellationToken cancellationToken) [0x000de] in <4678cc7d86684b659921915f01406e6d>:0 
  at Emby.Server.Implementations.Library.LibraryManager.UpdateItems (System.Collections.Generic.List`1[T] items, MediaBrowser.Controller.Entities.BaseItem parent, MediaBrowser.Controller.Library.ItemUpdateType updateReason, System.Threading.CancellationToken cancellationToken) [0x00057] in <4678cc7d86684b659921915f01406e6d>:0 
  at Emby.Server.Implementations.Library.LibraryManager.UpdateItem (MediaBrowser.Controller.Entities.BaseItem item, MediaBrowser.Controller.Entities.BaseItem parent, MediaBrowser.Controller.Library.ItemUpdateType updateReason) [0x00014] in <4678cc7d86684b659921915f01406e6d>:0 
  at MediaBrowser.Controller.Entities.BaseItem.UpdateToRepository (MediaBrowser.Controller.Library.ItemUpdateType updateReason) [0x0000c] in <54eb7a58944a40ffb2d688502bd6f5ee>:0 
  at MediaBrowser.Providers.Manager.MetadataService`2[TItemType,TIdType].SaveItem (MediaBrowser.Controller.Providers.MetadataResult`1[T] result, MediaBrowser.Model.Configuration.LibraryOptions libraryOptions, MediaBrowser.Controller.Library.ItemUpdateType reason, System.Threading.CancellationToken cancellationToken) [0x00057] in <21475520e74343d3b1e5c36f0be60586>:0 
  at MediaBrowser.Providers.Manager.MetadataService`2[TItemType,TIdType].RefreshMetadata (MediaBrowser.Controller.Entities.BaseItem item, MediaBrowser.Controller.Providers.MetadataRefreshOptions refreshOptions, System.Threading.CancellationToken cancellationToken) [0x00690] in <21475520e74343d3b1e5c36f0be60586>:0 
  at MediaBrowser.Controller.Entities.BaseItem.RefreshMetadata (MediaBrowser.Controller.Providers.MetadataRefreshOptions options, System.Threading.CancellationToken cancellationToken) [0x0019c] in <54eb7a58944a40ffb2d688502bd6f5ee>:0 
  at MediaBrowser.Providers.Manager.ProviderManager.RefreshItem (MediaBrowser.Controller.Entities.BaseItem item, MediaBrowser.Controller.Providers.MetadataRefreshOptions options, System.Threading.CancellationToken cancellationToken) [0x00092] in <21475520e74343d3b1e5c36f0be60586>:0 
  at Emby.Server.Implementations.Services.ServiceController.GetTaskResult (System.Threading.Tasks.Task task) [0x000ef] in <4678cc7d86684b659921915f01406e6d>:0 
  at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync (Emby.Server.Implementations.HttpServer.HttpListenerHost appHost, MediaBrowser.Model.Services.IRequest httpReq, MediaBrowser.Model.Services.IResponse httpRes, Emby.Server.Implementations.Services.RestPath restPath, System.String responseContentType, System.Threading.CancellationToken cancellationToken) [0x001da] in <4678cc7d86684b659921915f01406e6d>:0 
  at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler (MediaBrowser.Model.Services.IRequest httpReq, System.ReadOnlyMemory`1[T] urlString, System.ReadOnlyMemory`1[T] localPath, System.Threading.CancellationToken cancellationToken) [0x00b52] in <4678cc7d86684b659921915f01406e6d>:0 
Source: mscorlib
TargetSite: Void Throw()

Share this post


Link to post
Share on other sites
jamesphw

This is not solved, but an update for developers: I actually had this same error (and same SQLitePCL.pretty.SQLiteException: Constraint: FOREIGN KEY constraint failed

) happen on a single-version media file. After restarting the server, both my single and multiple-versioned files can be identified correctly using both IMDB and TMDB identifiers. I actually can't reproduce the issue anymore.

Share this post


Link to post
Share on other sites
Luke

Hi there, can you please attach the complete emby server log? Thanks.

Share this post


Link to post
Share on other sites
jamesphw
3 minutes ago, Luke said:

Hi there, can you please attach the complete emby server log? Thanks.

@Luke  For privacy reasons I'd rather not post the full server log on a public form, but happy to share it directly with you. What's the best way to share it directly?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...